Hi, consider this policy:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <SetOAuthV2Info async="false" continueOnError="false" enabled="true" name="update"> <DisplayName>update</DisplayName> <AccessToken ref="request.formparam.accessToken"/> <Attributes> <Attribute name="{request.formparam.attribute}" ref="request.formparam.value"/> </Attributes> </SetOAuthV2Info>
If I post "attribute=test&value=foo" it sets the "{request.formparam.attribute}" instead of the "test" attribute - the variable is not resolved.
Apart from security considerations, would something like this be possible?
Thank you!
I believe it's expected & as per design. As of today, I don't think we support reference flow variables for attribute name property.
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |