Why can't I use property expansions in Auth Repository? Is there a workaround?
I was hoping to use hardcoded OAuth tokens in my project, but protect them somehow so they aren't clear text in source control. I was hoping I could use Custom Project Properties that were read from a file that was ignored by source control. This doesn't appear to work. Property expansions don't appear to work here. Does anyone know a way to do this?Solved1.1KViews0likes3CommentsGetting Authorization code using private key JWT as client authenticatoin.
We are implementing UK open banking and authenticating client using JWS Client Assertion using a private key JWT. Post request to autorisation end point is send with signed JWT in body. It is then redirected to user authentication (username and password). Authorization code is recieved which then need to be exchanged with access token. Not able to achieve this using OAthu2 in soapui as there is no option to use signed JWT (in body). Also is it possible to get the access token is two step ? 1. Get authorizatio code by sending the signed JWT in the body 2. Exchange authorization code with access token1.7KViews0likes1Comment