I am wondering, with the latest release, can we protect resources with CA SSO JWT authentication scheme, and use Google Sign-in, a certified OpenID Connect OP, for authentication? This would act similar to previously documented OAuth social sign-on.
I see several docs on CA SSO as the OP, but not the other way around. There is a section in docops “CA Single Sign-On as OpenID Connect Resource Server” and that refers to an “Authorization Provider Dialog” section, which says the Authorization Server Base URL is the Access Gateway? Should that not be the OP URL (Google) in this scenario? And in the Client Dialog, do i use the Client ID and secret provided by Google? I cannot manually enter the Client Secret from Google. Is this setup just not do-able yet? Any thoughts?
Source: New feed
{pubDate}