In latest release the Red Hat SSO extension itself adds so called Authentication request which is visible on:
Authentication settings page
Buddy Icon context menu in activity bar
Status bar as a hat
When one uses any of the mentioned controls the ext redirects to the default browser for authentication and after successful login 1. Creates registry.redhat.com account in Registries settings
Activates developer subscription in current active podman VM
That was done to simplify implementation and user experience for summit. With no dependent extension published that works just fine. But when OpenShift Local extension start using Red Hat SSO extension to let user to pull pull-secret without copy paste commands that executed after sign in look a bit out of context. Same can be told about developer sandbox connection configuration, when extension needs the SSO token to talk to sandbox registration service and has nothing to do with building Bootable Images based on RHEL.
Considering above problems the SSO Extension should not:
Add authentication request
Assume registry access configuration is required
Or subscription activation is required
All three item should be delegated to dependent extensions because SSO extension is not aware of the reason for authentication request.
In latest release the Red Hat SSO extension itself adds so called
Authentication request
which is visible on:When one uses any of the mentioned controls the ext redirects to the default browser for authentication and after successful login 1. Creates registry.redhat.com account in Registries settings
That was done to simplify implementation and user experience for summit. With no dependent extension published that works just fine. But when OpenShift Local extension start using Red Hat SSO extension to let user to pull pull-secret without copy paste commands that executed after sign in look a bit out of context. Same can be told about developer sandbox connection configuration, when extension needs the SSO token to talk to sandbox registration service and has nothing to do with building Bootable Images based on RHEL.
Considering above problems the SSO Extension should not:
All three item should be delegated to dependent extensions because SSO extension is not aware of the reason for authentication request.
Related issues: