Hi Kristof,

There is probably more than one way to do this, but here's at least one thing you can try. I'm going to assume you are doing this at a SAML IDP and are looking for information on the SP-partner?

If so, consider using an Access Policy - this definitely has access to the SAML request via:

var protocolContextJSON = (function() {    var protocolContext = context.getProtocolContext();    var protocolContextReturn = {};    protocolContextReturn["request"] = "" + protocolContext.getAuthnRequest();    protocolContextReturn["FederationId"] = "" + protocolContext.getFederationId();    protocolContextReturn["PartnerId"] = "" + protocolContext.getPartnerId();    protocolContextReturn["FederationName"] = "" + protocolContext.getFederationName();    protocolContextReturn["PartnerName"] = "" + protocolContext.getPartnerName();    return protocolContextReturn;})();// Now your authn request should be in protocolContextJSON["request"]

You can also access the current user's credential in the access policy. From that you could extract tagvalue_session_index. Eg:

var sessionindex = null;var user = context.getUser();if (user != null) {    sessionindex = user.getAttribute("tagvalue_session_index");}

Using IDMappingExtCache, you can use the session index as the key, and store as the value whatever details you want from the authentication request. 

Then later in your federation mapping rule you can retrieve those values (information about the SSO request) from IDMappingExtCache as the stsuu in the mapping rule will also contain the tagvalue_session_index.

Make sense?

Hi Kristof,

There is probably more than one way to do this, but here's at least one thing you can try. I'm going to assume you are doing this at a SAML IDP and are looking for information on the SP-partner?

If so, consider using an Access Policy - this definitely has access to the SAML request via:

var protocolContextJSON = (function() {    var protocolContext = context.getProtocolContext();    var protocolContextReturn = {};    protocolContextReturn["request"] = "" + protocolContext.getAuthnRequest();    protocolContextReturn["FederationId"] = "" + protocolContext.getFederationId();    protocolContextReturn["PartnerId"] = "" + protocolContext.getPartnerId();    protocolContextReturn["FederationName"] = "" + protocolContext.getFederationName();    protocolContextReturn["PartnerName"] = "" + protocolContext.getPartnerName();    return protocolContextReturn;})();// Now your authn request should be in protocolContextJSON["request"]

You can also access the current user's credential in the access policy. From that you could extract tagvalue_session_index. Eg:

var sessionindex = null;var user = context.getUser();if (user != null) {    sessionindex = user.getAttribute("tagvalue_session_index");}

Using IDMappingExtCache, you can use the session index as the key, and store as the value whatever details you want from the authentication request. 

Then later in your federation mapping rule you can retrieve those values (information about the SSO request) from IDMappingExtCache as the stsuu in the mapping rule will also contain the tagvalue_session_index.

Make sense?

Hi Kristof,

There is probably more than one way to do this, but here's at least one thing you can try. I'm going to assume you are doing this at a SAML IDP and are looking for information on the SP-partner?

If so, consider using an Access Policy - this definitely has access to the SAML request via:

var protocolContextJSON = (function() {    var protocolContext = context.getProtocolContext();    var protocolContextReturn = {};    protocolContextReturn["request"] = "" + protocolContext.getAuthnRequest();    protocolContextReturn["FederationId"] = "" + protocolContext.getFederationId();    protocolContextReturn["PartnerId"] = "" + protocolContext.getPartnerId();    protocolContextReturn["FederationName"] = "" + protocolContext.getFederationName();    protocolContextReturn["PartnerName"] = "" + protocolContext.getPartnerName();    return protocolContextReturn;})();// Now your authn request should be in protocolContextJSON["request"]

You can also access the current user's credential in the access policy. From that you could extract tagvalue_session_index. Eg:

var sessionindex = null;var user = context.getUser();if (user != null) {    sessionindex = user.getAttribute("tagvalue_session_index");}

Using IDMappingExtCache, you can use the session index as the key, and store as the value whatever details you want from the authentication request. 

Then later in your federation mapping rule you can retrieve those values (information about the SSO request) from IDMappingExtCache as the stsuu in the mapping rule will also contain the tagvalue_session_index.

Make sense?

Hi Kristof,

There is probably more than one way to do this, but here's at least one thing you can try. I'm going to assume you are doing this at a SAML IDP and are looking for information on the SP-partner?

If so, consider using an Access Policy - this definitely has access to the SAML request via:

var protocolContextJSON = (function() {    var protocolContext = context.getProtocolContext();    var protocolContextReturn = {};    protocolContextReturn["request"] = "" + protocolContext.getAuthnRequest();    protocolContextReturn["FederationId"] = "" + protocolContext.getFederationId();    protocolContextReturn["PartnerId"] = "" + protocolContext.getPartnerId();    protocolContextReturn["FederationName"] = "" + protocolContext.getFederationName();    protocolContextReturn["PartnerName"] = "" + protocolContext.getPartnerName();    return protocolContextReturn;})();// Now your authn request should be in protocolContextJSON["request"]

You can also access the current user's credential in the access policy. From that you could extract tagvalue_session_index. Eg:

var sessionindex = null;var user = context.getUser();if (user != null) {    sessionindex = user.getAttribute("tagvalue_session_index");}

Using IDMappingExtCache, you can use the session index as the key, and store as the value whatever details you want from the authentication request. 

Then later in your federation mapping rule you can retrieve those values (information about the SSO request) from IDMappingExtCache as the stsuu in the mapping rule will also contain the tagvalue_session_index.

Make sense?

Hi Kristof,

There is probably more than one way to do this, but here's at least one thing you can try. I'm going to assume you are doing this at a SAML IDP and are looking for information on the SP-partner?

If so, consider using an Access Policy - this definitely has access to the SAML request via:

var protocolContextJSON = (function() {    var protocolContext = context.getProtocolContext();    var protocolContextReturn = {};    protocolContextReturn["request"] = "" + protocolContext.getAuthnRequest();    protocolContextReturn["FederationId"] = "" + protocolContext.getFederationId();    protocolContextReturn["PartnerId"] = "" + protocolContext.getPartnerId();    protocolContextReturn["FederationName"] = "" + protocolContext.getFederationName();    protocolContextReturn["PartnerName"] = "" + protocolContext.getPartnerName();    return protocolContextReturn;})();// Now your authn request should be in protocolContextJSON["request"]

You can also access the current user's credential in the access policy. From that you could extract tagvalue_session_index. Eg:

var sessionindex = null;var user = context.getUser();if (user != null) {    sessionindex = user.getAttribute("tagvalue_session_index");}

Using IDMappingExtCache, you can use the session index as the key, and store as the value whatever details you want from the authentication request. 

Then later in your federation mapping rule you can retrieve those values (information about the SSO request) from IDMappingExtCache as the stsuu in the mapping rule will also contain the tagvalue_session_index.

Make sense?