STS Token layout
we are exploring the potential of using our existing STS service with the Robotics component. The runtime would call STS to get the token (same one that we use for WFI, so the user name is in the xxx@AFII format) and Pega Platform would need to decrypt that token.
Our question is on the format of that token and how to parse it to get the user identifier. Since Pega is obviously doing this as part of WFI processing we were wondering if there is documentation on that layout or if there is any routine that can be shared that parses it.
Also, when the WFI runtime on a users workstation calls the STS service, where does that token get stored so that it included in the data pushes to PegaCloud? Is it in the registry? In the app memory or written to the users workstation somewhere?
***Edited by Moderator Marissa to update platform capability tags****
Keep up to date on this post and subscribe to comments