| ||||||||
| Line: 7 to 7 | ||||||||
|---|---|---|---|---|---|---|---|---|
IdeaThe idea of integrating Autograph in Shibboleth SSO is to make the handling of attributes more transparent to IdP members. | ||||||||
| Changed: | ||||||||
| < < |
When they visit a Service Provider the first time they are redirected to Autograph. In Autograph they are able to view the attributes released to this Service Provider and to change the release status of attributes. They will see the effect of their changes immediately, assumed a Service Provider description is available. (e.g. the service feature 'email notification' becomes unavailable after denying the release of the email address). | |||||||
| > > |
When they visit a Service Provider the first time (this depends on the configuration) they are redirected to Autograph. In Autograph they are able to view the attributes released to this Service Provider and to change the release status of attributes. They will see the effect of their changes immediately, assumed a Service Provider description is available. (e.g. the service feature 'email notification' becomes unavailable after denying the release of the email address). | |||||||
| Another benefit of Autograph's integration in the SSO profile is that the IdP members can be asked to aggree to certain legal terms before their attributes are shared accross the Federation. | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
-- MoritzTheile - 17 Aug 2006 | |||||||
| > > |
<< to Autograph main page | |||||||
Autograph's integration in the Single Sing On (SSO) profile | ||||||||
| Changed: | ||||||||
| < < |
The Idea | |||||||
| > > |
Idea | |||||||
|
The idea of integrating Autograph in Shibboleth SSO is to make the handling of attributes more transparent to IdP members.
When they visit a Service Provider the first time they are redirected to Autograph. In Autograph they are able to view the attributes released to this Service Provider and to change the release status of attributes. They will see the effect of their changes immediately, assumed a Service Provider description is available. (e.g. the service feature 'email notification' becomes unavailable after denying the release of the email address). Another benefit of Autograph's integration in the SSO profile is that the IdP members can be asked to aggree to certain legal terms before their attributes are shared accross the Federation. | ||||||||
| Added: | ||||||||
| > > |
-- MoritzTheile - 17 Aug 2006 | |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
||||||||
-- MoritzTheile - 17 Aug 2006
Autograph's integration in the Single Sing On (SSO) profile | ||||||||
| Line: 5 to 4 | ||||||||
|---|---|---|---|---|---|---|---|---|
Autograph's integration in the Single Sing On (SSO) profile | ||||||||
| Added: | ||||||||
| > > |
The IdeaThe idea of integrating Autograph in Shibboleth SSO is to make the handling of attributes more transparent to IdP members. When they visit a Service Provider the first time they are redirected to Autograph. In Autograph they are able to view the attributes released to this Service Provider and to change the release status of attributes. They will see the effect of their changes immediately, assumed a Service Provider description is available. (e.g. the service feature 'email notification' becomes unavailable after denying the release of the email address).Another benefit of Autograph's integration in the SSO profile is that the IdP members can be asked to aggree to certain legal terms before their attributes are shared accross the Federation. | |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
Autograph's integration in the Single Sing On (SSO) profile | |||||||