I configured a custom authentication module that authenticates users against Active Directory. It works fine when portal desktop is accessed without a gateway. But via gateway, it tries to authenticate against LDAP not the custom auth module. Is there any configuration setting that I'm missing here? All the componenets are JES4.
Thanks in advance,
lakshmi
You can specify the organization and authentication module in the URL like this:
https://sra.domain.com?org=MyOrg&module=AD
You can also configure the default organization in the platform.conf.default file:
sra.domain.com.defaultOrg=MyOrg
This will make it so that you can access the organization without specifying it on the command line.
- Jim
Jim,
This is what I was using earlier:
Without Gateway: http://myportalserver.dev.com:8180/amserver/UI/Login?org=employee -->Working
Via Gateway: https://mygateway.dev.com:8443/employee
Now I'm trying to log in with the following URLs:https://mygateway.dev.com:8443?org=employee
https://mygateway.dev.com:8443?org=employee&module=AD
https://mygateway.dev.com:8443/amserver/UI/Login?org=employee
All the above are returing Authentication failed.
The other option that you suggested is having a property in platform.conf file. I have this file in 2 boxes. One on Portal server box and the other on the Gateway box. Do I need to add this in both the files?
The platform.conf file just needs to be modified on the gateway.
You need to get it working with the URL parameters first, since that is the most straightforward way to specify the organization and auth module. Once that is working, then you can modify the platform.conf file so that you don't need to have the org in the URL.
- Jim
