Versions Compared

Old Version 15

changes.mady.by.user Steven Maglio

Saved on

compared with

New Version 16

changes.mady.by.user Steven Maglio

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • All Assumptions from Usage: Application to Resource Server Requirements
  • Campus IdM system will support the password grant type.
  • It is a requirement that ucsbNetId's for Service Accounts must be unique and non-changing.
    • They should be able to be reused. But the expectation is that if a service account changes names, it will need to have it's permissions reestablished in all downstream systems.

...

Ticket(s)TitleUser StoryPriorityNotes

Identify End UserAs a Client Developer, I need a way to provide the Resource Service with authenticated identity information about who is using my application.
Status
colourGreen
titlemust have
  • Should need both Service Account ucsbNetId and password, and the End User ucsbNetId and password.
  • OAuth call should go against Apigee OAuth endpoint.
    • Apigee will pass through the call to Campus IdM
    • The Campus IdM response will pass through back to the client

Authenticate End UserAs a Campus IdM Admin, I need authenticate the End User before the Resource Service can grant access.
Status
colourGreen
titlemust have

Verify End User in Resource Server (Service)As a Resource Service Developer, I need a way to provide the Resource Service with authenticated identity information about who is using my resource.
Status
colourGreen
titlemust have

Authorize End User & App in Resource Server (Service)As a Resource Service Developer, I need to be able to lookup permissions and enforce access authorization.
Status
colourGreen
titlemust have
  • For application specific permissions, the Authorization Provider should be determined by the Resource Service Developer. This can be something created solely by the developer for their needs or it can be a campus provided solution.

Verify App in Resource Server (Service)As a Resource Service Developer, I need to be able to provide the Resource service with authenticated identity information about the client application using my resource.
Status
colourYellow
titlenice to have
  • The PingIdentity server will need to validate the access_token given.
  • This should use the PingIdentity servers validate_bearer grant type.
  • The response should include the Client Service Account ucsbNetId. There does not seem to be a way to get the Client Service Account ucsbCampusId. Because of this, it is a requirement that ucsbNetId's for Service Accounts must be unique and non-changing.
    • They should be able to be reused. But the expectation is that if a service account changes names, it will need to have it's permissions reestablished in all downstream systems.

...

 
QuestionOutcomeDecision DateCan you use the Introspection Endpoint from the Resource Service? Is the original client_id and client_secret required? Or will it work with the client_id of the Resource Service (Registrations SVC ucsbNetId)?What does the Introspection Endpoint return for the password grant type? Does it return both the End User ucsbNetId and the client_ID (Client App ucsbNetId)?It returns both the sub (End User ucsbNetId) and the client_id (Client App ucsbNetId).