This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 43%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAH%3C/text%3E%3C/svg%3E)
I noticed the great accepted answer to the following question...
I wonder if there is a similar approach you could suggest for metadata items in a CpimIssuerTechnicalProfile used as a "Send Claims" orchestration step?
The suggested approach of using a pre-condition will not be suitable, as you are only allowed to specify a single "Send Claims" step (policy fails to upload).
Ideally I'd like to be able to set some token properties (token-lifetimes) dynamically.
Many Thanks.
This is not possible. You will have to create 2 user journeys.
--
Please let us know if this answer was helpful to you. If so, please remember to mark it as the answer so that others in the community with similar questions can more easily find a solution.
Thanks for the reply Alfredo. Yes - that is the conclusion I was coming to.
I was trying to avoid having 2 policies. As such, do you know if there is any way to either conditionally invoke an alternative user journey from the RelyingParty (or indeed somehow switch between multiple Relaying Parties)? It feels like I am clutching at straws here :)
If it has to be 2 policies then that's the way it has to be.
Thanks for your help.
There's none trough the custom policy engine itself (subjourneys won't work in your case).
I did have some success by specifying multiple "SendClaims" steps, and then arbitrarily specifying one as the DefaultCpimIssuerTechnicalProfileReferenceId in the user journey tag (I could not find any documentation on this).
This works as I'd want it to for Implicit Flow, the appropriate JwtIssuer is used based on the pre-condition. However, when using Code Flow, only the Issuer specified as Default is used regardless of pre-condition (presumably the default is used when redeeming the code, rather than remembering the issuer from the original auth user journey).
I think I've exhausted this now, thanks for you help.