ictxPremappedInfo--Authentication Context Premapped User Info

This describes the premapped user information that will be added to the authentication context, or was parsed from the authentication context. See eServer Implementation Notes for details on platform-specific details.

Premapped User Information

The structure ictxPremappedUserInfo_t describes the authentication information used for authentication tokens that support authentication information. New fields may be added to the end of this structure. On a parse operation the fields will be returned if they exist in the authentication context. Code that has been rebuilt with the new structure may access these new fields. A version supplied with the build information indicates which new fields have been provided.

The layout for ictxPremappedUserInfo_t follows:

typedef struct ictxPremappedUserInfo
{
    char           * user;            /* Mapped user                 */
    char           * registry;        /* Registry used for the mapping  
                                      operation.                      */
    char           * mappingSource;    /* Indicates what type of
                                        information was used as the
                                        source for the mapping lookup
                                        operation.                    */
    char           * mappingQualifiers;/* Additional information that
                                        was used for the mapping
                                        operation.                   */
    char           * implemSpecific;  /* Additional data, optional    */
} ictxPremappedUserInfo_t;

Field Descriptions

user  

The name of the premapped user.

registry  

The name of the user registry that was used for the mapping lookup operaton.

mappingQualifiers  

Additional information that was used for the mapping operation. If EIM was used for the mapping lookup operation then this would be the additionalInformation parameter.

implemSpecific  

This is implementation specific data that would be added to an authentication context. This value may be NULL. The sender and the receiver must agree on format and content of this data. The recommended layout for this data would be a series of the following:

<LABEL>xxxxx</LABEL><DATA>yyyyy</DATA>

An example would be:

<LABEL>TCPIP address</LABEL><DATA>9.5.6.132</DATA>

Build Information

The premapped user information used for building of an authentication context is contained in the ictxPremappedInfo structure. The layout for ictxPremappedInfo follows:

typedef struct ictxPremappedInfo
{
    enum ictxPremappedInfoFormat format;
    union
    {
        ictxPremappedInfoFormat0_t format0;
    } premappedInfo;
} ictxPremappedInfo_t;

Field Descriptions

format  

Valid values for the format are:

enum ictxPremappedInfoFormat  {
    ICTX_PREMAPPED_INFO_FORMAT_0
};

When format is ICTX_PREMAPPED_INFO_FORMAT_0 (0), the premappedInfo field must contain an ictxPremappedInfoFormat0_t structure.

typedef struct ictxPremappedInfoFormat0
{
    int                   version;
    ictxPremappedUserInfo_t  * premappedInfo;
} ictxPremappedInfoFormat0_t;

version  

The version indicates which fields are available in the the authInfo field. Version 0 corresponds to the initial structure defined here. In the future if new fields are added to the premappedInfo structure and the users wants to pass that information in for a build they can indicate the new version of the structure that they are providing.

premappedInfo  

This is the structure that contains the premapped user information fields.

eServer Implementation Notes

1. AIX implementation details:
   • None.
2. Linux implementation details:
   • None.
3. i5/OS implementation details:
   
   • None.
4. Windows implementation details:
   • None.
5. z/OS implementation notes:
   
   • None.