Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Mukesh,

The request context only contains the context related to the most recently received HTTP request from the user. So, after the user POSTs response to 2FA method, the original request at the start of the flow is lost.

You'll need to add code in an early infomap (maybe the validate session one if that is JavaScript?) to read the values you need and store in the response context so that they can be read again later in the authentication policy flow.

Jon. 

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Jon,

I'm not sending password, newPassword and confirmPassword in the first request. sending after 2FA.

Even flow is that, suppose the user wants to change the transaction password. First, he/she has to authenticate with 2FA once the user is authenticated then we need to ask the user for passwords.

------------------------------
Mukesh

Original Message:
Sent: Tue December 22, 2020 04:17 AM
From: Jon Harry
Subject: ISAM - Getting null value in InfoMap

Hi Mukesh,

The request context only contains the context related to the most recently received HTTP request from the user. So, after the user POSTs response to 2FA method, the original request at the start of the flow is lost.

You'll need to add code in an early infomap (maybe the validate session one if that is JavaScript?) to read the values you need and store in the response context so that they can be read again later in the authentication policy flow.

Jon. 

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Jon,

I'm not sending password, newPassword and confirmPassword in the first request. sending after 2FA.

Even flow is that, suppose the user wants to change the transaction password. First, he/she has to authenticate with 2FA once the user is authenticated then we need to ask the user for passwords.

------------------------------
Mukesh

Original Message:
Sent: Tue December 22, 2020 04:17 AM
From: Jon Harry
Subject: ISAM - Getting null value in InfoMap

Hi Mukesh,

The request context only contains the context related to the most recently received HTTP request from the user. So, after the user POSTs response to 2FA method, the original request at the start of the flow is lost.

You'll need to add code in an early infomap (maybe the validate session one if that is JavaScript?) to read the values you need and store in the response context so that they can be read again later in the authentication policy flow.

Jon. 

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Jon,

I'm not sending password, newPassword and confirmPassword in the first request. sending after 2FA.

Even flow is that, suppose the user wants to change the transaction password. First, he/she has to authenticate with 2FA once the user is authenticated then we need to ask the user for passwords.

------------------------------
Mukesh

Original Message:
Sent: Tue December 22, 2020 04:17 AM
From: Jon Harry
Subject: ISAM - Getting null value in InfoMap

Hi Mukesh,

The request context only contains the context related to the most recently received HTTP request from the user. So, after the user POSTs response to 2FA method, the original request at the start of the flow is lost.

You'll need to add code in an early infomap (maybe the validate session one if that is JavaScript?) to read the values you need and store in the response context so that they can be read again later in the authentication policy flow.

Jon. 

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Mukesh,

Can you confirm that the headers being sent are the same on the working request vs the non working request? And could you show us more context of where the error message is coming from?

You may also need to switch from POST on the last request to PUT, as on apiauthsvc the method can overwrite the operation.

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?

Hi Mukesh,

Can you confirm that the headers being sent are the same on the working request vs the non working request? And could you show us more context of where the error message is coming from?

You may also need to switch from POST on the last request to PUT, as on apiauthsvc the method can overwrite the operation.

Hello Team,

I have written infoMap to change one of the user attributes let's say Transaction password(custom attribute).

and then created a policy and access it as API. It's working fine

code for reference.
//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// logic to update user attribute with scim API's.

but when I added branching with 1 branch for MAC OTP and other Branches with TOTP in Policy. it's working fine till the branching step once it moves to the change transaction password step. infoMap receives a null value for all the request attributes.

code for reference.

//imported required packages

var username = context.get(Scope.SESSION, "urn:ibm:security:asf:response:token:attributes", "username");

var password = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "password"));

var newPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "newPassword"));

var confimPassword = utf8decode(context.get(Scope.REQUEST, "urn:ibm:security:asf:request:parameter", "confimPassword"));

// getting all attribute from request as null

// logic to update user attribute with scim API's.

// dynamic_url is taken from the previous api call(action attribute).

Can anyone help with the same?