Difference between revisions of "Client Authentication Agent"
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
Provides local management of user authentication. | Provides local management of user authentication. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Responsibilities in Profiles== | ==Responsibilities in Profiles== | ||
| − | |||
The responsibilities placed on this actor in the context of each [[Profiles| Profile]] is summarized here. For the actual specifications, refer to the [[Frameworks|Technical Framework]]. | The responsibilities placed on this actor in the context of each [[Profiles| Profile]] is summarized here. For the actual specifications, refer to the [[Frameworks|Technical Framework]]. | ||
A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product [[Statements|Integration Statement]]. | A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product [[Statements|Integration Statement]]. | ||
| + | ===[[Enterprise User Authentication]]=== | ||
| + | This Profile depends on the actor to: | ||
| + | * communicate authentication information to the [[Kerberos Authentication Server]], | ||
| + | * receive a [[TGT]] or Service Ticket from a [[Kerberos Authentication Server]], | ||
| + | * perform internal TGT management, | ||
| + | * provide an appropriate ticket as part of the connection or session management for another protocol, | ||
| − | === | + | ===[[Patient Synchronized Applications]]=== |
| − | + | * establish a secure context session connection with the [[Context Manager]] so as to be able to perform User Subject changes in the common context, | |
| − | + | * initiate context changes for user subject by supplying new context values, | |
| − | + | * notifies the [[Context Manager]] that it will no longer be participating in the context management session. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==See Also== | ==See Also== | ||
| − | + | This actor is often grouped with: [[Time Server]], [[Time Client]] | |
| − | |||
| − | |||
| − | This actor is often grouped with: | ||
| − | |||
This page is based on the [[Actor Template]] | This page is based on the [[Actor Template]] | ||
Latest revision as of 14:57, 28 November 2006
Provides local management of user authentication.
Responsibilities in Profiles
The responsibilities placed on this actor in the context of each Profile is summarized here. For the actual specifications, refer to the Technical Framework.
A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product Integration Statement.
Enterprise User Authentication
This Profile depends on the actor to:
- communicate authentication information to the Kerberos Authentication Server,
- receive a TGT or Service Ticket from a Kerberos Authentication Server,
- perform internal TGT management,
- provide an appropriate ticket as part of the connection or session management for another protocol,
Patient Synchronized Applications
- establish a secure context session connection with the Context Manager so as to be able to perform User Subject changes in the common context,
- initiate context changes for user subject by supplying new context values,
- notifies the Context Manager that it will no longer be participating in the context management session.
See Also
This actor is often grouped with: Time Server, Time Client
This page is based on the Actor Template