The goal of this how-to is to explain how you can manage your application's users with the Users management application.
Fill in the credentials of an administrator user and press the 'Login' button.
And you're in! Welcome to the Users management console.
Select the 'Users' tab and click on 'Create new User';
Fill in the user data as depicted;
Press the 'Save' button, a success feedback message should be displayed;
And you're done! This user is ready to login in any application.
Users can be assigned with a Role to be granted access to specific screens. In addition you'll also be able to use Roles to enable/disable access to other application elements like buttons, containers, etc. or to condition your application's logic.
Roles are defined at development time in Service Studio and are automatically made available in the Users application.
To create a Role, go to Service Studio and under Logic, right click the roles folder and pick 'Add Role'. You'll have to publish your application, for the role to be made available in the Users application.
To assign a Role to a user, you'll need to access the Users application at "http://<SERVERNAME>/Users" (where <SERVERNAME> is the host name of the server you're working on):
You may need to group users to simplify mangement of large sets of users. You can do this by Using Groups to aggregate users or roles:
Make sure the Platform Server is inside the Active Directory Domain you want to your users to authenticate with.
Type the following URL in your web browser: "http://<SERVERNAME>/Users" where <SERVERNAME> is the host name of the server you're working on. The login page should be displayed
Click the 'Configure Authentication' link on the right
Fill in the form as depicted below and click 'Save'
And you're done!
Can someone explain to me the relationship between http://<SERVERNAME>/Users and the "Users & Roles" page in http://<SERVERNAME>/Lifetime? It seems that users created in the Lifetime environment do not have access to apps in Outsystems Now. Does one need to add a separate user-id in the Users environment for that? How does app authorization in Outsystem Now work?
In http://<SERVERNAME>/Users you have all the Runtime users (your application end users)
In http://<SERVERNAME>/Lifetime you have all your developers.
Renato Gonçalves wrote:
So, a developer does not have access to an app unless he/she also has a seperate account in the users environment?
Imagine, for example, a Production environment where you want your developers/consultants to be able to publish and correct the applications, but you don't want them to access the application itself has it has sensitive data. This way you can control this.
Some clarification is needed here.
* All user records are associated with an eSpace.
* Every eSpace has a property that chooses which eSpace is its "User Provider".
* The only users that an eSpace can "see" are users that are associated with the "User Provider" eSpace.
* BY DEFAULT your new eSpaces are created with the "Users" eSpace as the "User Provider". This may be changed at any time.
This means that 1) you do not NEED to use "Users" and 2) applications can completely separate their user groups simply by having different User Providers and 3) all eSpaces in an Application (and related Applications) should share the same User Provider, or else they won't know what's going on.
I guess this is an appropriate place to ask my question:
What to do if you lost access to /Users? I only have one administrator as far as i know, and we don't know the password anymore. admin/admin doesn't work.
How can I reset the password or any other means to regain access?
Kilian Croese wrote:
You should contact OutSystems Support, they can help you recover the Admin user password.
I am using Outsystems platform 10.
It is configured to use active directory authentication for application login
How do i add an existing user in active directory into the application users list