Authorisation
Auth
AvailableAnswers “may user X do Y” ower HTTP.
Ower HTTP, Auth tells a service gin user X may dae Y. It handles authorisation anerly an relies on the caller tae ken wha the user is. It disna sign oniebody in, store passwords, issue tokens or manage sessions. The model haes users, roles an permissions, an a user hauds a permission exactly whan ane o thair roles hauds it.
Wha it is for. Services that need role-based access control and dinnae want tae maintain their ain roles and permissions tables.
- Status
- Available
- Pairt o
- Core platform
- Product site
- auth.rodmena.app
- Tags
- Access controlRoles and permissionsAe decision
Whit it dis
-
Ae quaisten
The API haes ane quaisten tae answer, “may user X dae Y”, an it answers it consistently for aw services.
-
Uisers, roles, permissions
Users get a role’s permissions throu membership o that role, an thair is naething mair tae model.
-
Authorisation anely
Passwirds, sessions an tokens are oot o scope an belang tae RODMENA ID.
-
Quick tae tak up
Acause a check is ane caa wi ane answer in a fixed response shape, a service can be brocht unner central access control in an efternuin.
Documentation and access details are on the product site, auth.rodmena.app. For a pilot, an integration or procurement questions, contact us.