Is it possible to add traditional login methods for application with Azure Ad SSO settings?
This is for dev testing only, since the app has many layers of approval and needs to be tested with different user info.
Seems like default user login is set with SSO and I don't want to change it on Users application, is it possible to do it on App module instead?
Yes, it is possible. You can keep Azure AD SSO as the default login and add a custom traditional login only in your App module for DEV testing. No need to change the Users application settings globally. Just make sure the custom login is restricted to non-production environments.
Please enlighten me on how to do it
For example, normally your app works like this:
User opens the application
It redirects to Azure AD SSO login
After Microsoft authentication, the user enters the app
Now for DEV testing, you may need to test different approval flows with multiple users without using real Azure accounts every time.
The “Developer Login” can be a simple custom screen with:
Username
Password
Example test users:
approver1
manager1
finance1
You can validate these users from a custom entity/table and create the session after successful login.
This way:
Azure AD SSO remains unchanged
No need to modify the Users application globally
Traditional login is available only for DEV/UAT testing purposes in your App module.
Apologize for this question, but how do I make a dev login page that works without userId or password? For traditional login method i previously worked, I use user and password.
But the employee data that I have consists of only employee data without userId or password.
is there a workaround to change user once your app already logged on SSO one time?
Hello @Samuel Susetia Davilantinov NugrahaIf I understand, your Application Login is made through Azure Ad.I'll assume you are in O11
For O11, you ALWAYS need a user in the OutSystems User entity, even when you use an external identity provider (like azure). Usually the system automatically creates the user in OutSystems when the user makes the first login through Azure (or any other external IDP).So, what happens in this case is that the user authentication is made "externally", but the user is still being logged in into the OutSystems environment (and it has a user defined in the User entity for that to happen).How to "bypass" the need to create a user in Azure for testing:1. Through the Users application, you can create Test users (in Dev) defining their user names, passwords and application roles.2. Then you can create a separated app with a custom login page/logic where you log in into OutSystems using the login actions from Users or System (this one does not require the password) with the test users. (Separate app is useful to avoid accidentally sending it to QA or PROD).3. O11 SSO will guarantee you can then enter the other application, as the user, as long as it has the correct roles the other application requires, will already be logged in (no need to log into Azure).You then test your application with your data, that will be associated to your test user.Basically, you don't even need to touch the code in the application you want to test.Hope this will help you.Cheers!