[db-wg] Personalised authorisation
- Previous message (by thread): [db-wg] Personalised authorisation
- Next message (by thread): [db-wg] Cancel
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Mon May 18 13:33:04 CEST 2015
On 15/05/15 09:27, Tim Bruijnzeels wrote: > Dear working group, > > Yesterday during the WG session we presented a proposal for > implementing personalised authorisation: > https://ripe70.ripe.net/wp-content/uploads/presentations/165-ripe70-pers-auth.pdf > https://ripe70.ripe.net/archives/video/123 > > As recorded in the first cut of the minutes: >> D. Personalised authentication (Tim Bruijnzeels, RIPE NCC) >> (See presentation) >> This will allow one click creation of person objects >> Maintain credentials in one place. >> Allow better auditing. >> Done by extending person object to have multiple optional auth: >> attribute >> This will ultimately allow existing auth: sso references to be >> cleaned up >> Last auth: attribute should not be removed from a person object >> that is used in an authorisation context. > > Of course, those of us with long memories remember the move of authentication from persons to maintainers. Plus ca change.... Nigel -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20150518/0c26a09d/attachment.html>
- Previous message (by thread): [db-wg] Personalised authorisation
- Next message (by thread): [db-wg] Cancel
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]