| Page Properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- An easy way to sign into the Developer Portal
- Preferably you would be able to sign in using the Campus SSO solution
- An easy way for Teams of Developers to manage Groups of Applications
- An easy way to associate Applications with Campus IdM Service Accounts for use with OAuth Authentication
- If possible, the ability to create a Campus IdM Service Account at the time of registering an Application
- An easy way to pass in an Apigee Client ID to an attribute on a Campus IdM Service Account
Out of Scope
Assumptions
- Campus IdM will support Application Accounts (Service Accounts).
- Application Accounts (Service Accounts) Description from ETSC (UCSB isDesk):
> 2018-05-25 10:06:09 - Laurie Branagan (Additional comments)
> App accounts were created to allow for programmatic access to the
> directory without embedding a person's credentials in the application. They
> were not scoped to be used for authorization beyond access to the
> directory. It's understood this utility is somewhat limited.
> If what you're requesting is non-person entities in the directory - That
> feature is on the roadmap document that the Identity Advisory Group drafted
> last year. It has not been implemented.
- Application Accounts (Service Accounts) Description from ETSC (UCSB isDesk):
- We will eventually integrate Developer Portal logins with Campus SSO.
...
Current Account and App Creation (WebSequenceDiagram Link)
Simple SSO and Service Account Association (WebSequenceDiagram Link)
...