Having a user interface where trusted users can assign privileges to lower-level folks is massively advantageous if you build it right, by comparison. You do need to make fine-grained control possible, to be able to roll up permission sets into predefined roles, and - a simple matter that evades many - assign multiple roles to a given user. Users frequently "wear multiple hats", as they say, and you need to account for that.
Authentication Is Largely Solved. Authorization Isn't
11–15 of 15 posts
Re: Authentication Is Largely Solved. Authorization Isn't
#12If anyone has a good book on setting up a good authorization model in a corporate environment, please pass it along.
Re: Authentication Is Largely Solved. Authorization Isn't
#13Clearly the problem is solved now:
“Minimum of 6 characters please”
bullet ricochet noises
“Special character please”
ninja roll
“I’M GONNNA NEED TO SEE SOME ID”
nuclear explosion
Re: Authentication Is Largely Solved. Authorization Isn't
#14Earlier quoted context omitted.
Yep, the king is currently SMS, which isn't good. I like passkeys, but somewhere between websites and browsers, even those aren't used in a consistent way. And idk why there are so many prompts before you're actually logged in with one. The name is also unclear. TOTP is way worse. It used to be kinda synonymous with Google Authenticator which had insane footguns for losing your codes. Now it's just inconsistent and w…
A very odd real example is how Sony went backwards with passkey compatibility on their apps. It's I think what happened when they tried to have a single OIDC setup instead of multiple (PSN was a totally separate setup for the longest time and had it solved, but other parts of Sony, on a separate system, was almost wholly incompatible. The merging of the two made it impossible for their current webkit implementations…