For a project we want to use a custom web api to deliver additional complex functionality. We already have a custom REST Web API which can provide the functionality we need, which uses oAuth 2 Azure AD authentication. When we use the workflow steps "Call HTTP Web Service" or "App Step" we receive authentication errors. The steps themselves don't really allow configuration for this. Is there a way we can use these an custom Web API which uses oAuth 2?
Solved! Go to Solution.
Thank you for your comment. We have created a solution that works for us:
Since we need to use usernames and passwords, it would be really helpfull to use the constant variables Ninxes offers on premises, but... it works :-).
I ll follow up on the explanation as well.
De : Cedric Oster <email@example.com>
Envoyé : mercredi 24 octobre 2018 16:34
À : GARREAU, Kenza
Objet : #Adv#: You have been mentioned by Cedric Oster in Re: Working with custom web api in Nintex Community
Nintex Community <https://community.nintex.com/?et=notification.mention>
You have been mentioned
by Cedric Oster<https://community.nintex.com/people/coster?et=notification.mention> in Re: Working with custom web api in Nintex Community - View Cedric Oster's reference to you<https://community.nintex.com/message/84616-re-working-with-custom-web-api?commentID=84616&et=notification.mention#comment-84616>
There were multiple steps involved and some steps can probably be bundled, but these are the steps we used:
Hope this helps!
Thanks a lot! In my case I was getting 'Authorization has been denied for this request' when using the token. It turned out to be because the 'resource' value used to get the token must match the web api's web.config 'ida:Audience' property, and in my case was 'api://<app_id>'.