Snippets and Thoughts of One Oracle Developer

S Sometimes I need to login as a specific user to verify what he/she can access and see. And most of the times I would like to login as me with a single button. So I created login page like this: So I can signup with any user I like or use the Google button to sign up via Google SSO. In corporates we would typically use Microsoft 365 SSO. To make this more secure, the login field, button and process behind are visible only to developers (users signed up in APEX Builder) thanks to my core.is_developer function used as authorization scheme on these components. You should also disable the login field, button and process on production. Best approach would be to assign a Build option and disable it. Or/and you can use the SSO authentication as default there. If I am not signed in APEX Builder, I will not have the option to sign as anyone: And here is the trick how to do this: Create Google SSO authentication Enable Switch auth scheme on your open door and SSO au

I I was very tired of filling out the forms for signing into the APEX Builder, so I decided to use the SSO there too. I wont cover how to get the credentials , but here is a great step by step article how to do that. So assuming you did setup your SSO credentials, log into INTERNAL workspace as ADMIN user. This could be the last time you have to sign in with a password, isn't that cool? At the top click on Manage Instance and Security and consider following changes: on Security tab change Allow Persistent Auth to Yes on Authentication Control tab under Development Environment Settings change Require User Account Expiration and Locking to No under Development Environment Authentication Schemes edit the SSO option To configure Google SSO, fill the fields carefully like this (use your own credentials obviously): Scope = profile,email Username = #email# Additional User Attributes = email,name For different providers parameters would var