Task #1536: resolve differences in listPrincipals() and getPrincipalInfo() - Infrastructure - DataONE Tasks

Task #1536

Story #725: Create Authentication and Access control design specifications

resolve differences in listPrincipals() and getPrincipalInfo()

Added by Matthew Jones over 13 years ago. Updated about 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ben Leinfelder

Category:

Documentation

Target version:

Maintenance Backlog

Start date:

Due date:

% Done:

100%

Milestone:

2011-Block-3

Product Version:

Story Points:

Sprint:

History

#1 Updated by Matthew Jones over 13 years ago

Category set to Documentation
Milestone set to 2011-Block-3

listPrincipals() and getPrincipalInfo() are currently close to identical -- need to chnage getPrincipalInfo() to differentiate it as applying to a Person, or maybe eliminate it altogether.

#2 Updated by Ben Leinfelder over 13 years ago

I've taken to thinking of getPrincipalInfo as:
getPrincipalInfo(cert, Types.Principal) returning Types.Person. This would allow someone who was trying to "verify" an identity to actually look up the details of the Principal in question. The cert might be optional depending on how much information about users is allowed to be public (or required if none is meant to be public).

#3 Updated by Ben Leinfelder over 13 years ago

Assignee changed from Matthew Jones to Ben Leinfelder

#4 Updated by Ben Leinfelder over 13 years ago

Status changed from New to Closed

getPrincipalInfo(cert, principal) now returns a Person representing the Principal argument (which includes equivalent IDs and Group membership details)