The REST API in question requires three parameters for authentication, a user Id, a password, and an applicationID. The item returned is a JSON Web Token (JWT). I have successfully defined a Login action with these parameters. But additional actions do not work because the JWT must be passed with "Bearer" prepended. In a number of other Power Apps I created, I used OAuth, and there was no issue, however in this app with a simple JWT being passed, the question becomes, which (if any) of the Security Authentication Types can be used? My initial though was to use API Key, however this has been unsuccessful. I also thought about using No authentication and simply use the PowerApps UI to make all of the calls, storing the JWT, however, this doesn't seem to be optimal to me.
Thanks so much for your reply! Yes, I was thinking that an Azure function might be the best way to handle. Will give it a try. Appreciate the response!
Based on the authentication parameters you've mentioned, I'm guessing you're looking for password (ROPC) grant type for OAuth, which I doubt MS will implement as it's no longer being maintained in the OAuth spec going forward, hence no such options available via the security UI section within the custom connector setup pages.
If this is still the only way the API you're using can generate bearer tokens, then perhaps you could setup a middle man that can generate the token and pass that token through to the destination api as part of the header (e.g an azure function), or do as you currently suggested, where you're generating a bearer token, then pass that token to whichever api you need to call as part of the header parameters.
WarrenBelz
770
Most Valuable Professional
stampcoin
494
MS.Ragavendar
399