Powerhouse Web user authentication

[Peter Bateman]

       HI Vaughn:
 
 
         When someone signs into PowerHouse Web they are part of
         UNKNOWN Application Security Class unless there username
         is in the WEBLOGONID list and WEBLOGONID is the selected . 
         Usernames in the UAF would not necessarily
         be identifiable to PowerHouse Web.
 
         I believe they have to be identified some other way;
         usually username and password.
         Has anyone got PowerHouse Web to work BCEIDs?
Regards,
Peter Bateman
 
VERSION 8.4E
PDL AND UTILITIES REFERENCE
     
WEBLOGONID username [[,] username]...
Assigns user names that are potential members of this ASC. Username is case sensitive.
When PowerHouse Web opens a dictionary it checks the ID method in the APPLICATION
SECURITY ID METHOD option of the SYSTEM OPTIONS statement. If the ID method is
WEBLOGONID, PowerHouse Web checks authenticated usernames against the list of usernames
in the WEBLOGONID option. If the authenticated username is listed in a WEBLOGONID option
of an ASC statement, the user becomes a member of that ASC and the KNOWN class. If an
authenticated username is not listed in any WEBLOGONID option of any ASC statement, the
user is treated as a member of the ANONYMOUS class and the UNKNOWN class.
If there is no authenticated username, or the ASC ID METHOD is not WEBLOGONID, the user
becomes a member of the ASC UNKNOWN.
 


Subject: Powerhouse Web user authenticationDate: Thu, 24 Apr 2008 12:54:23 -0700From: Vaughn.Smith at gov.bc.caTo: powerh-l at lists.sowder.com

We have PH Web running on an Alpha OpenVMS. The documentation says that user authentication is handled by handled outside of PH and the dictionary. Can the authentication reference the OpenVMS user authorization file or does it need to be something else entirely? Thanks! Vaughn SmithSenior Business AnalystInformation & Technology Management BranchMinistry of Advanced Education___________________________________________ email: Vaughn.Smith at gov.bc.caphone: 250.387.8907fax: 250.356.0033 From the Cognos PH Web documentation: 
Authentication and Access Control To restrict access to known users, some Web servers allow you to specify that a username and password must be entered before a specific folder or file is accessed. Authentication is the process of prompting for and verifying the username and password. Access control ensures that resources such as folders and files are only accessible to authenticated users. Refer to your Web server documentation to find out how to set up authentication and access control for your Web server. Note that the username and password list used for authentication is separate from PowerHouse Web and the PowerHouse dictionary. Maintaining the username and password list is done outside of PowerHouse Web. By requiring a password to access the PHCGI, you can ensure that only known users can access PowerHouse Web applications. However, most applications have some pages that you want to protect, and some that can be open to public view. In this case, you use two copies of the PHCGI, one as a protected resource requiring authentication to access and the other unprotected. Once you have both protected and unprotected copies of the PHCGI, you still need to control access at the page level. Controlling page access is required because you can't prevent someone from typing a URL pointing to the unprotected PHCGI using a page that is supposed to be protected. PowerHouse Web can use the authenticated username to control access to the page. In addition, the username can be used to control access to items and records through application security specified in the dictionary. 
_________________________________________________________________
Turn every day into $1000. Learn more at SignInAndWIN.ca
http://g.msn.ca/ca55/213
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20080425/9219e765/attachment.html