User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
5mo
one can only write so much specification document involving OIDC in one day

and that is good

no one should have to do more of this
2
0
4
0
User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
5mo
codeberg.org/polyphony/polyproto-dot-org/commit/eac734612bdedb70f8b53ccbf1ab6da592ecf799
2
1
3
0
User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
5mo
This clears another big blocker in integrating OIDC into polyproto. One of the last big ones, actually
1
0
1
0
User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
5mo
Specifically, the commit translates a concept which already existed previously in the spec, called "sensitive solutions", to work with OIDC. What we call "sensitive solutions" is basically the "enter your password to confirm this action" you already know from other applications, but in polyproto. :3
1
0
1
0
User avatar
AstraLuma @astraluma@tacobelllabs.net
5mo
@star love a good sudo dialog
1
0
1
0
User avatar
celeste_hearts_lesbianceleste_hearts_transceleste_hearts_demisexual flori_ava_star:~cursor_blinking @star@amazonawaws.com
5mo
@astraluma sudo but they send you straight to AzureAD >:3
1
0
0
0
User avatar
AstraLuma @astraluma@tacobelllabs.net
5mo
@star sudon't!
0
0
0
0