BestP 4 FedAppDevelopers

Best Practices for Federated Application Developers

Attribute Handling by Service Providers

Options
Use and Discard (IdPs' Default First Choice)
Persist (If You Have a Justified Requirement)
Be Provisioned (Bulk, On/Just Before First Access)
Tiering or Bundling of Attributes for Service Classes, for uApprove
Asymmetry

Coding for Option-ality

Discovery: Services (like iTunes U) vs. "True" Federated Apps

Representing Permissions for access control

Groups
Roles & Permissions
Ticket/tokens/Roles

Help Desk

SPs: How Do We Scale

To 100s of IdPs?
To Scores of Federations?

Some Advice for IdPs

Some Advice for Federations (An InterFed Discussion)

...

  • No labels