Open tommparekh opened 3 years ago
If I remove OAuth setup from skipper server (just HTTPS config), then I can log on to data flow server dashboard using OAuth. However, I continue to see application status as undeployed (while those are deployed successfully). I can see all the streams I created but seeing as undeployed.
Not sure if this is an issue? In data flow config, I have already mapped all the roles correctly (view and others).
I am following documentation here to setup OAuth authentication for my SCDF and skipper server. Both, data flow and skipper servers are deployed on open source cloud foundry.
identity-provider-azure
Here is a text from the link that is confusing:
App registration is where OAuth clients are created to get used by OAuth applications. At minimum, you need to create two clients, one for the Data Flow and Skipper servers and one for the Data Flow shell, as these two have slightly different configurations. Server applications can be considered to be trusted applications while shell is not trusted (because users can see its full configuration).
As SCDF dashboard is a UI application, OAuth setup will be using authorization flow. The documentation suggest to use the same setup of SCDF OAuth client, to setup Skipper server. However, skipper server is not accessible using UI but appears to be more of a system to system communication (data flow server - skipper). So should we use the same OAuth client as data flow server?
For your reference, I am also seeing below error with current setup (skipper OAuth setup matching data flow server)
Thanks, Mihir