This content has been marked as final. Show 7 replies
The login channel uses a template file with the organization name hardcoded in the URL. This file is:
Where enterprise_sample is the name of your desktop type. The blog's name is new_enterprise_sample.
Edit this file and replace all instances of "org=EnterpriseSample" with the name of the organization you created for the new sample. The blog's name for this is newEnterpriseOrgYouCreated, so the string that replaces it should be "org=newEnterpriseOrgYouCreated".
<form action="<dtpc:getLoginURL/>?org=EnterpriseSample&goto=<dtpc:getDesktopURL/>" target="_parent" method="POST" name="loginForm" enctype="application/x-www-form-urlencoded" onsubmit="return loginFormValid();">
<dtpc:getLoginURL/>?org=EnterpriseSample&goto=<dtpc:getDesktopURL/> will generate an url like "http://portal.example.com/amserver?org=EnterpriseSample&goto=/portal/dt".
The parameter "org=EnterpriseSample" tells Access Manage to authenticate the user in EnterpriseSample organization.
I modified the anonymous.jsp file like your instruction , changing org=EnterpriseSample to org=new_Organization . But I can't still login the new portal site with accounts of new_Organization.
It seems we need to modify somewhere else so that the new site could work properly .
I think maybe the author of the article , Jim Faut , should know the exact way to make his sample work .
Are there any Sun guys , portal gurus , Jim Faut could help me to sovle this problem ?
My apologies, my fix was for using a custom login channel for the anonymous enterprise desktop as used in portal 7.2. Since editing the login url in ASCTabContainerProvider/anonymous.jsp didn't work, verify that you can log in your new users from /amconsole. After the login succeeds, enter /portal in the url and see if they get the correct portal desktop. Should that work, doublecheck the edits to the login URL. I've been able to edit that file to allow only the developer sample user to login by changing the org= parameter.
I know this is an old post but I have added to Jim Fauts article how to do this, see below:
Seeing that alot of people are facing the same problem regarding new user being unable to authenticate against the new Portal, I did a bit of digging up and managed to get it to work. See the steps I followed below, but first follow Jim's example above then after follow the example below:
After configuring the roles and loading display profile change the following settings, so that the new user's you create can authenticate.
I did the following to get my new users to authenticate:
On Solaris I opened the following file: /var/opt/SUNWportal/portals/csonline/desktop/csonline/Login/display.template
I changed all occurrences of org=EnterpriseSample to my new organization o=fiction
I also changed the Organization display profile document, replaced every occurrence of o=EnterpriseSample with the name of my organization fiction, in this case I replaced all values that are o=EnterpriseSample,dc=test,dc=co,dc=za
After configuration you might get a module denied error Authentication Module Denied
Depending on which module you are using, in my case I am using LDAP so I also changed all occurrences of Membership to LDAP inside the display.template file.
After the above changes restart your web container container for the changes to take place and Bobs your uncle.
Thats it. Its alive !!!
Hope this helps