FEDERATED SINGLE SIGN-ON (F-SSO) REQUEST PROCESSING USING A TRUST CHAIN HAVING A CUSTOM MODULE

• US 20090125972A1
• Filed: 11/14/2007
• Published: 05/14/2009
• Est. Priority Date: 11/14/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Salmon, Parley Avery, Wardrop, Patrick Ryan, Hinton, Heather Maria
• Granted Patent: US 8,141,139 B2
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/126 the source of the received data

Abstract

Federated single sign on (F-SSO) uses a token service that fulfills requests by executing a module chain comprising a set of modules. F-SSO runtime processing is enhanced by enabling a federated entity user to define a custom module to include in the chain. The custom module includes one or more name-value pairs, wherein a given name-value pair has a value that may be validated against an entity-defined rule. The rule is determined during the processing of the custom module based on one or more invocation parameters of the module chain. In a runtime operation, F-SSO begins in response to receipt of a token. In response, the processing of the module chain that includes the custom module is initiated. During processing of the custom module, an attempt is made to validate the value of a name-value pair based on the rule. If the value of the name-value pair based on the rule can be validated, processing of the module chain continues. This approach enables finer granularity on the information that can be asserted or required as part of an F-SSO flow.

Claims

1. A method, operative within a federated environment in which a token service fulfills requests by executing a module chain comprising a set of modules, comprising:

responsive to receipt of a token, initiating processing of the module chain;

during processing of the module chain, attempting to validate a value of a name-value pair based on a rule, wherein the rule is determined based on one or more invocation parameters of the module chain; and

returning a response.

2. The method as described in claim 1 wherein the value of the name-value pair is attempted to be validated upon execution of a custom module within the module chain.

3. The method as described in claim 2 wherein the rule is associated with the custom module in an off-line process.

4. The method as described in claim 1 wherein, if the value of the name-value pair is validated, the response is an output token.

5. The method as described in claim 1 wherein, if the value of the name-value pair cannot be validated, the response is an error.

6. The method as described in claim 1 wherein, if the value of the name-value pair cannot be validated, the response is a condition authorization.

7. The method as described in claim 2 wherein the invocation parameters of the module chain include an identity of the custom module and an issuer of the token.

8. The method as described in claim 1 wherein the rule identifies a condition that must be satisfied by a user of a first entity attempting to execute a federated single sign-on (F-SSO) to the federated environment.

9. The method as described in claim 8 further including re-using the rule for a user of a second entity.

10. The method as described in claim 1 further including:

generating an internal representation of information in the token; and

evaluating the internal representation to determine if all name-value pairs expected to be in the token are contained within the token;

wherein the evaluating step is performed on a name of each name-value pair.

11. The method as described in claim 1 wherein the value in the name-value pair is associated with a single value or a multi-value.

25. The method as described in claim 1 wherein the module chain is a dynamic chain.

12. A method, operative within a federated environment in which a token service fulfills requests by executing a module chain comprising a set of modules, comprising:

defining a custom module to include one or more name-value pairs, wherein a given name-value pair has a value that may be validated against a rule;

responsive to receipt of a token, initiating processing of the module chain that includes the custom module;

during processing of the custom module, attempting to validate the value of a name-value pair based on the rule, wherein the rule is determined during the processing of the custom module based on one or more invocation parameters of the module chain; and

returning a response.

13. The method as described in claim 12 wherein the invocation parameters are one of:

an identity of the custom module, and an identity of token issuer.

14. The method as described in claim 12 wherein the token is received upon a user of a first entity attempting a federated single sign-on (F-SSO) to the federated environment.

15. The method as described in claim 12 further including:

generating an internal representation of information in the token; and

evaluating the internal representation to determine if all name-value pairs expected to be in the token are contained within the token;

wherein the evaluating step is performed on a name of each name-value pair.

16. A computer program product for use in a federated environment in which a token service fulfills request by executing a trust chain comprising a set of modules, comprising:

a computer-readable medium having processor-executable instructions for performing the following steps;

responsive to receipt of a token, initiating processing of the module chain;

during processing of the module chain, attempting to validate a value of a name-value pair based on a rule, wherein the rule is determined based on one or more invocation parameters of the module chain; and

returning a response.

17. The computer program product as described in claim 16 wherein the value of the name-value pair is attempted to be validated upon execution of a custom module within the module chain.

18. The computer program product as described in claim 16 wherein, if the value of the name-value pair is validated, the response is an output token.

19. The computer program product as described in claim 16 wherein, if the value of the name-value pair cannot be validated, the response is an error.

20. The computer program product as described in claim 16 wherein, if the value of the name-value pair cannot be validated, the response is a condition authorization.

21. The computer program product as described in claim 16 wherein the invocation parameters of the module chain include an identity of the custom module and an issuer of the token.

22. A data processing system for use in a federated environment in which a token service fulfills requests by executing a module chain comprising a set of modules, comprising:

means for defining a custom module to include one or more name-value pairs, wherein a given name-value pair has a value that may be validated against a rule;

means responsive to receipt of a token for initiating processing of the module chain that includes the custom module;

means operative during processing of the custom module for attempting to validate the value of a name-value pair based on the rule, wherein the rule is determined during the processing of the custom module based on one or more invocation parameters of the module chain; and

means for returning a response.

23. The data processing system as described in claim 22 wherein the invocation parameters are one of:

an identity of the custom module, and an identity of token issuer.

24. The data processing system as described in claim 22 further including:

means for generating an internal representation of information in the token; and

means for evaluating the internal representation to determine if all name-value pairs expected to be in the token are contained within the token;

wherein the evaluating step is performed on a name of each name-value pair.