| Div |
|---|
| Wiki Markup |
|---|
{div2:class= | | | } BestP 4 FedAppDevelopers {div2}
{toc}
-----
h3. Best Practices for Federated Application Developers
h4. Attribute Handling by Service Providers
h5. Options
h6. Use and Discard (IdPs' Default First Choice)
h6. Persist (If You Have a Justified Requirement)
h6. Be Provisioned (Bulk, On/Just Before First Access)
h5. Tiering or Bundling of Attributes for Service Classes, for uApprove
h5. Asymmetry
h4. Coding for Option-ality
h4. Discovery: Services (like iTunes U) vs. "True" Federated Apps
h4. Representing Permissions for access control
h5. Groups
h5. Roles & Permissions
h5. Ticket/tokens/Roles
h4. Help Desk
h4. SPs: How Do We Scale
h5. To 100s of IdPs?
h5. To Scores of Federations?
h3. Some Advice for IdPs
h3. Some Advice for Federations (An InterFed Discussion)
h3. ...
FedAppDevelopers |
Best Practices for Federated Application DevelopersAttribute Handling by Service ProvidersOptions 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 uApproveAsymmetryCoding for Option-alityDiscovery: Services (like iTunes U) vs. "True" Federated AppsRepresenting Permissions for access controlGroupsRoles & PermissionsTicket/tokens/RolesHelp DeskSPs: How Do We ScaleTo 100s of IdPs?To Scores of Federations? Some Advice for IdPsSome Advice for Federations (An InterFed Discussion)... |