Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] SSO integration - grouper 2.3.0

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] SSO integration - grouper 2.3.0

Chronological Thread 
  • From: Jeff McCullough <>
  • To: "Hyzer, Chris" <>
  • Cc: Gouper Users List <>
  • Subject: Re: [grouper-users] SSO integration - grouper 2.3.0
  • Date: Mon, 22 Aug 2016 17:47:16 -0700
  • Ironport-phdr: 9a23:xKfekBc5uTHGKhnyfFepAmOelGMj4u6mDksu8pMizoh2WeGdxc66YB7h7PlgxGXEQZ/co6odzbGJ4+a9AidZvN6oizMrTt9lb1c9k8IYnggtUoauKHbQC7rUVRE8B9lIT1R//nu2YgB/Ecf6YEDO8DXptWZBUj22Dwd+J/z0F4jOlIz3krnqo9yAKzlP0XCdcKF/NlH+hgXLt9Jcyd9nIaYg2BbTinpTcKJL3W5uIxSekwuqtemq+5s20SletboE/OVdVaH9Yqs4BehaATooNmsd7sDxthTHQBrJ63cBBDZF2iFUChTIuUmpFqz6tTH3468kgHGX

Hi Chris,

For the grouper.ui.authentication.http.header parameter, I tried no value, $REMOTE_USER and REMOTE_USER. None of these changed the error behavior.

Tomcat server.xml doesn’t have that or any similar setting. 

For diagnostics of tomcat/CAS, I installed a small cas-client app that reads/displays REMOTE_USER via a request.getRemoteUser() call. It works as expected. 

Do you have any other ideas?


On Aug 20, 2016, at 7:33 AM, Hyzer, Chris <> wrote:

Is it $REMOTE_USER or just REMOTE_USER?   I don’t think you need to change that setting as you said…  but try editing it. 
Do you have tomcat server.xml setting:
<Connector port="8552" protocol="AJP/1.3" connectionTimeout="600000" request.tomcatAuthentication="false"
      URIEncoding="UTF-8" />
Or whatever the tomcat authn setting for your version is…
From:  [] On Behalf Of Jeff McCullough
Sent: Friday, August 19, 2016 10:35 PM
To: Gouper Users List <>
Subject: [grouper-users] SSO integration - grouper 2.3.0
Hi all,
I’ve run into a snag with SSO integration this time around. I’ve actually done the procedure multiple times on other versions, and it was very easy to setup, no problems. This time with grouper 2.3.0, no workie.  Here’s what I’ve done:
I have the CAS 3.4.2 java client integrated with tomcat version 7 running on java 1.8. 
I removed the security-constraints, login-config, and security-role from the web.xml file. 
I modified the struts-config.xml with callLogin set to, though the previous step is where I start seeing the below error.
This seemed redundant (because REMOTE_USER is the default), but found it in a email thread where someone else was having the same issue.
I modified grouper.ui.authentication.http.header = $REMOTE_USER
Lastly I added the debug statement ( = DEBUG) in log4j with the result of:
2016-08-19 19:24:55,632: [http-bio-8443-exec-2] DEBUG GrouperUiFilter.remoteUser(636) -  - httpServletRequest.getRemoteUser(): null, $REMOTE_USER header: null, REMOTE_USER attribute: null, session.getAttribute(authUser): null, remoteUser overall: null
I’ve confirmed that the CAS client is in fact returning REMOTE_USER with correct user id. I modified the index.jsp within the grouper UI to display it, so I know grouper is seeing it. Yet, I get the error message:
You have an anonymous session since you are not logged in, but this section requires you to be logged in. Maybe No username found. Your identity provider might not be sending your username to this application. Either you need to use a different identity provider, or ask your IT department to send your username to this application.
Thanks in advance for any insights you may have.

Archive powered by MHonArc 2.6.19.

Top of Page