Notification links requiring users to re-authenticate to PPM.
Notification links that are sent to a user's email inbox are requiring users to re-authenticate to PPM even though they already have an open session. We are using a clustered environment, and our servers sit behind a BIGIP load balancer. Does anyone know of any settings that I have overlooked in the set up?
Re: Notification links requiring users to re-authenticate to PPM.
Hello Heather, how are the links placed in the notification? Are you using tokens to create them at runtime or have you placed them manually in the notification definition? If so, the URL must match between the link in the notification and the URL the user entered in his browser. We had a similar situation where users entered a DNS alias (like "ppm") and later clicked on a link in a notification with an URL like http://server.domain.tld/... They had to login again. Regards Sascha
# # Secondary Server Details (to be used by WHPPPM02P) # @node com.kintana.core.server.KINTANA_SERVER_NAME=Service_Secondary com.kintana.core.server.SERVER_NAME=WHPPPM02P com.kintana.core.server.RMI_URL=rmi://WHPPPM02P:1175/KintanaServer com.kintana.core.server.HTTP_PORT=8091
And we do have the users typing in PPM as far as the URL and accessing PPM. I checked the link in the notification and it points to a token.
With this being a clustered environment, I'm not sure what to change as far as the com.kintana.core.server.BASE_URL