🛠️Setup Authorization code flow

Setup overview in OData connector configuration

Setup

Auth URL

Get Authority URL value from IFS Cloud.

Obtaining Authentication related URLs from IFS Cloud

Access Token URL

Get Access token URL value from IFS Cloud.

Obtaining Authentication related URLs from IFS Cloud

IFS IAM Client details (Client Id, Client Secret)

Create IAM client like in example.

Name IAM client so that it can be identified as being used by Flow. Also adding postfix describing authentication type would be a good idea.

Example name: NC_Flow_AuthCode, Novacura_AuthCode

Use same name for same type of IAM client in all customers IFS Cloud instances.

Scope(s)

Set default value of openid microprofile-jwt to OData connectors Scope(s).

WIP - Additional query parameters

?

WIP - Flow Server User Setup

Flow User Id can be different IFS User Id.

Add IFS userid to user specific connector setup.

OPEN ISSUE: is connector level user name Identity or Directory Id from IFS? Depends on if user is authenticated in IFS or external IDP?

WIP - Effect to Flow development

Flow apps using connector with Runtime authentication type Authorization Code authentication cannot be debugged in Studio.

For flow developer this means that prior debugging connector in flow must be changed to connector using Runtime authentication type of Client Credentials or Password Credentials. Alternatively, if flow has a lot of fragments and changing the connectors in all fragments takes a lot of time you can have copy of the flow (+ fragments) using connector using Runtime authentication type of Client Credentials or Password Credentials.

Notice that possible to have connector using Password Credentials requies that IFS User has password defined in IFS and SSO login is disabled.

If flow uses projections that require authentication as actual user in IFS, then debugging can only be done by running tests in NC client.