Can I create an Atrium user id such as GUEST without that id being an AS400 Userid?
We want to create a public userid that can only see url's and applications that have no authority concerns.
Creating a GUEST id without an AS400 userid?
-
- New User
- Posts: 12
- Joined: Wed Jan 19, 2011 3:42 pm
- First Name: Roderic
- Last Name: Vosburgh
- Company Name: McGard
- City: Orchard Park
- State / Province: New York
- Zip / Postal Code: 14127
- Country: United States
- Contact:
- David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: Creating a GUEST id without an AS400 userid?
Atrium can be setup to use a validation list for authentication. A validation list is an iSeries object that you can use to define a table of users/passwords that the HTTP server will authenticate against.
By default, Atrium is configured to use OS profile authentiction. However, we do provide sample directives in the HTTP server configuration that show how to use validaiton lists.
You'd need 2 instances of Profound UI / Atrium if you are also interested in using it for OS profiles.
To get started with validation lists in fresh instance of Profound UI / Atrium, you would:
1. Create a validation list object PROFOUNDUI/PUIVLDL using the CRTVLDL command.
2. Use the IBM Web Administration tool to create an initial user for yourself in the validation list.
3. Give user profiles QTMHHTTP/QTMHHTP1 *ALL authority to the validation list object.
4. Comment/uncomment the directives as specified in the http server configuraiton file to set it up for validation list authentication.
5. Sign into Atrium for the first time using your profile in the validation list. This will set this profile up as the Administrator in Atrium.
6. From here on, you can add/remove/change users in the valiation list using the interface in Atrium.
When setup this way, your jobs will always run as user profile QTMHHTP1, but you can check the environment variable REMOTE_USER in the job to get the validation list user profile name.
By default, Atrium is configured to use OS profile authentiction. However, we do provide sample directives in the HTTP server configuration that show how to use validaiton lists.
You'd need 2 instances of Profound UI / Atrium if you are also interested in using it for OS profiles.
To get started with validation lists in fresh instance of Profound UI / Atrium, you would:
1. Create a validation list object PROFOUNDUI/PUIVLDL using the CRTVLDL command.
2. Use the IBM Web Administration tool to create an initial user for yourself in the validation list.
3. Give user profiles QTMHHTTP/QTMHHTP1 *ALL authority to the validation list object.
4. Comment/uncomment the directives as specified in the http server configuraiton file to set it up for validation list authentication.
5. Sign into Atrium for the first time using your profile in the validation list. This will set this profile up as the Administrator in Atrium.
6. From here on, you can add/remove/change users in the valiation list using the interface in Atrium.
When setup this way, your jobs will always run as user profile QTMHHTP1, but you can check the environment variable REMOTE_USER in the job to get the validation list user profile name.
Who is online
Users browsing this forum: No registered users and 0 guests