Cutom object to store data for reference

Identity Security Cloud (ISC) ISC Discussion and Questions
1

In IdentityIQ we have custom object to perform/store some data for re use.
Do we have same future is avaiable in IDN, If i want to store some data how can we store.

Thanks
Naveen

2

Hi Naveen,

In what context are you trying to store data? Is this for use in a transform or a rule? Also, what kind of data are you storing? I don’t believe IDN has a custom object for data storage, but that doesn’t mean your use case can’t be solved other ways.

4

Hi Colin,

I have raised a post in the community, check for reference.

https://community.sailpoint.com/t5/IdentityNow-Forum/Web-service-Connector-Bearer-Authorization-refresh-token-after/m-p/219631#M10333

I am trying to integrate a System with the WebServices Direct connector. We are authorizing this system using Bearer Token,

  1. We have an endpoint to refresh the token, check the Token1 attachment for a reference. The response will be looks like the below.
    {
    “access_token”: “8oY2aSqKfdlEBvFlylzRGYA”,
    “token_type”: “bearer”,
    “expires_in”: 899
    }

  2. We have an endpoint to fetch the users, this endpoint authorization type is “Bearer Token”, refresh token endpoint repose access_token will pass to users endpoint. Check the attachment user’s endpoint. but the token is valid for 899 seconds only.

  3. I have written before operation rule to generate a new token every time but I want to utilize the first token only within the given period (899) after need to generate a new token. How can I generate a new token once it is expired? How to check if the token is expired or not? based on will generate a new token.

If any one have similar kind problem faced let me know how did we solved. But in IdentityIQ I know like we will store it in custom object like token generation time, access_token and expire_time values and will calculate the time difference in before operaation rule and we can achieve but in IDN how to do we can store and fetch the values.

user endpoint2 (1)
user endpoint2 (1)809×231 21.7 KB

RefreshToken1 (1)
RefreshToken1 (1)720×436 78.6 KB

Thanks
Naveen

5

I think IDN’s rules are very similar to IIQ. There should be a “transientValues” Map object that is persisted between runs. You could try using it to see if you can store the expiration date of the token. Here is a snippet to show you how to get the “transientValues” map. Once you have it, you can perform all of the usual operations on a Java Map object.

import connector.common.Util;

Map transientValues = (Map) application.getAttributeValue("transientValues");
if (null == transientValues) {
    transientValues = new HashMap();
    application.getAttributes().put("transientValues", transientValues);
}

// Perform the usual Java Map functions to set a new key to hold your
// expiration date if it doesn't already exist.  For each run of this rule,
// check if the token is expired.  If it is, then generate a new token,
// calculate the new expiration date, and then set the key to the new date.
6

Hi Colin,

It worked, I missed the document. But if any static data want to store in IDN how do we can, if it is IdentityIQ we can use Custom object.