Value of REMOTE_USER is always "Not set. SSO may not be enabled or you may not be accessing Splunk via your proxy server" in sso debug

[arcngoanhtuan]

I had enabled sso on my Splunk server (version 5) on CentOs machine. In the sso debug, I saw that:
SSO settings
- SSO Enabled: Yes
- ...
- splunkweb SSO Mode: permissive

Splunkweb settings
- ...
- Is the incoming request IP in splunkweb's list of trustedIPs?: Yes. SSO will be used to authenticate this request.

Remote user HTTP header:
- Remote User HTTP Header: REMOTE_USER
- Value of REMOTE_USER: Not set. SSO may not be enabled or you may not be accessing Splunk via your proxy server.

I didn't know how to configure the proxy server to map the REMOTE_USER.

I wrote a small website based Asp.net to add value of REMOTE_USER in the header of HttpWebRequest and connect to above configured Splunk server. But it always stops at the Splunk login screen instead of passing throught it via sso.

So, can anyone help me to solve this problem.

Thank you and sorry for my poor English.

[dart]

What proxy server are you using?
A basic example configuration for Apache is available on the wiki.

[arcngoanhtuan]

thank you so much for your help. I made it works finally. That was only the problem in my web.config file.