Hi Edmundo;

  Since both PB and OKTA support the REST API - I would like to suggest that you have a look at this integration through that mechanism.

FYI:  https://developer.okta.com/code/rest/

Regards ... Chris

I would suggest upgrading to PB 2019.  The REST client has been greatly enhanced since PB 2017 and it now directly supports tokens without you having to do your own implementation.  https://docs.appeon.com/appeon_online_help/pb2019/whats_new/ch01s04.html#Enhanced_RESTClient_object_in_beta_2

Hi Edmundo, 

In PowerBuilder 2019 R2 beta (https://www.appeon.com/developers/pb-2019r2-beta.html) we have added a new WebBrowser control.  We added the control actually for the purpose of loading the webpage in PowerBuilder that allows users to specify the authorization username/password.  So now if you want to call an Okta URL for login and then capture the OIDC token, please make sure to test it with the newly-introduced WebBrowser in 2019 R2 beta.

Best regards, Julie

Thanks for the replies.

I've already implemented Powerbuilder - Okta integration using the Resource Owner Password flow and Client Credentials flow using Powerbuilder 2019 and it's oAuth tokens.

On the Resource Owner Password flow, the Powerbuilder app captures username and password and sends it to Okta on an oAuth token object in Powerbuilder 2019.

The requirement though is to call an Okta URL for log-in and then capture the OIDC token after Okta has authenticated the user. This flow model is called Authority Code grant flow which are mainly used by web apps. 

One way to send "anything" back to a PB app from any web app using just a URL is to create a custom URL protocol handler that:

• Knows how to trigger events in your PB app
• Listens to whatever URL protocol you decide to use

You can install custom URL protocol handlers on Windows clients via Windows registry.

Alternatively you need your web app to call some REST service when your token is ready - and your PB app to poll that REST service until that token is available. Remember to do everything secured since this is a security token you don't want to expose.

Authority Code is primarily used by web apps because it is quite hard to allow calls from one web app (the login app) to a native win32/win64 app without breaking the security sandbox. I have used custom URL protocol to do that.

I'd recommend using REST service with Password Flow with the OauthClient object.