--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/cd4c4195-f8e3-4c2e-9b0e-373288e6c211%40googlegroups.com.
I'm glad you're having a least partial success with Dataverse and Shibboleth. :)I'm a little confused about your set up. How many installations of Dataverse do you have?For the installation that's giving an error, after you log in do you see attributes at https://demo.dataverse.org/Shibboleth.sso/Session (for your hostname)?Thanks,Philp.s. If you'd like your installation to be on our map, please feel free to open an issue at https://github.com/IQSS/dataverse-installations/issues :)
On Fri, May 29, 2020 at 9:58 AM Thierry Louge <th....@gmail.com> wrote:
--Hi all!We've been using Dataverse for some months now, and would like to provide this service to our users (we run a computing centre).We plan to use Shibboleth for authenticating users. So far, so good we made tests with shibboleth and Dataverse on the same machine and it works like a charm.Now, we run several services apart from Dataverse and we'd like to authentify users once and for all.Dataverse is served in a machine that is behind an apache proxy.This apache reverse-proxy runs shibboleth and authentifies users. This works. When the users goes to the Dataverse that runs on another machine, the parameters of the authenfication are not accessible for Dataverse.The glassfish server error is the following:[2020-05-29T14:19:12.438+0200] [glassfish 4.1] [INFO] [] [edu.harvard.iq.dataverse.Shib] [tid: _ThreadID=28 _ThreadName=http-listener-1(3)] [timeMillis: 1590754752438] [levelValue: 800] [[
The SAML assertion for "Shib-Identity-Provider" was null. Please contact support.]]What we don't figure out at the moment, is that if we launch a php page on the machine hosting Dataverse and we gather those parameters (the "Shib-Identiyi-Provider" mentioned in the error, for example) we do find them. But for some reason, Dataverse doesn't.Last thing, we stopped the shibboleth daemon on the machine hosting dataverse before doing those tests.If anyone figured out how to make an equivalent configuration running, we'd appreciate some help, or any clue on something that could lead us on the way.Thanks in advance, and cheers!
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/cd4c4195-f8e3-4c2e-9b0e-373288e6c211%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/cd4c4195-f8e3-4c2e-9b0e-373288e6c211%40googlegroups.com.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/5b2d997f-6c6c-4f4f-874c-acad8448fd6d%40googlegroups.com.