Please note that we have been able to locate and upload the missing images to this article.  Hopefully this will help.

David, this is great, appreciate your efforts!!

- please see updated article. Hope this helps, let us know if you need further assistance!

 

Just to expand on the original posting with the available option using the Convert Time token and the time offset calculations. The original rule above can be implemented without using a GCV as shown below. Using this example, with the 1 year hard coded in the Rule, the GCV used previously is not required.

Figure 1: Policy Rule using the Convert Time token, instead of XPath calculations, to set the Login Expiration Time to 1 year after the Login Time

<policy> <rule> <description>Set Account to Disable 1yr After Last Login</description> <comment xml:space="preserve">Set the Login Expiration time to be one year after the current login time. Uses the Convert Time token with a 1 year offset.</comment> <conditions> <and> <if-class-name mode="nocase" op="equal">User</if-class-name> <if-op-attr name="Login Time" op="available"/> </and> </conditions> <actions> <do-set-src-attr-value class-name="User" name="Login Expiration Time"> <arg-value type="string"> <token-convert-time dest-format="!CTIME" dest-tz="UTC" offset="1" offset-unit="year" src-format="!CTIME" src-tz="UTC"> <token-op-attr name="Login Time"/> </token-convert-time> </arg-value> </do-set-src-attr-value> </actions> </rule> </policy>

Figure 2: Policy Rule using Time Token XML details

To maintain flexibility of code, GCVs could (should?) be incorporated for the "offset" and "offset-unit" values by manually editing the XML code with something like:

Figure 3: Revised Policy Rule with GCVs for offset and offset-unit values highlighted.

<policy> <rule> <description>Set Account to Disable 1yr After Last Login</description> <comment xml:space="preserve">Set the Login Expiration time to be one year after the current login time. Uses the Convert Time token with a 1 year offset.</comment> <conditions> <and> <if-class-name mode="nocase" op="equal">User</if-class-name> <if-op-attr name="Login Time" op="available"/> </and> </conditions> <actions> <do-set-src-attr-value class-name="User" name="Login Expiration Time"> <arg-value type="string"> <token-convert-time dest-format="!CTIME" dest-tz="UTC" offset="~gv-offsetAmount~" offset-unit="~gv-offsetUnit~" src-format="!CTIME" src-tz="UTC"> <token-op-attr name="Login Time"/> </token-convert-time> </arg-value> </do-set-src-attr-value> </actions> </rule> </policy>

Figure 4: Revised Policy Rule XML details using GCVs for offset and offset-unit values.

The second option above will require that the GCVs for "gv-offsetAmount" and "gv-offsetUnit" be defined for this Rule to work.

Hopefully the combination of the original posting and the options noted above provides ideas on how similar actions can be incorporated in your solutions.

Cheers,

D

Hello @6423241,

I'm sorry about the missing images but I will get in touch with the product team to get information that is up to date.

Note that the article is 10 years old, surely there are newer documents. Stay tuned! 

 

Through the various moves of this content from Drupal to workpress to Khoros, they tried to copy all the materials over to the new system each time.

For some number of articles (Far too many of mine, which pisses me off greatly) they were using an external server for those images, not the native blogging software.  That server is gone.  Thus the images as well. Alas.

This looks like it might be a useful article, but all the content is in links and all the links are broken. 

 

 

The newer versions of IDM has an "offset" functionality in the time convert function that will eliminate the requirement to calculate seconds, etc.

Where the offset value is defined, just time the GCV name, starting and ending with a "~", ~gcvname~. Remember to select the unit, minute, month, year, etc.