-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
user login at localhost:8000 #1
Comments
Hi Emil, Thank you for your interest in this repository. I believe there can be some errors in the SP and other parts of the testbed, I'll try to look into them during the week. In the meantime you might want to have a look at circulation-saml-test repository. It does contain LDAP, Shibboleth IdP, and two different SPs and all of them are proxied through nginx to port 80 of your localhost (if you try to run it, please consider this and that you might need to explicitly grant access to port 80 to the Docker daemon on your system). Regards, |
Hi Viacheslav, |
Hi Viacheslav, |
Hi Viacheslav, |
Hello,
I have tried your project on Ubuntu 18.04. I had to uncomment the 4 lines in the docker-compose.yml to get the sp to build. Also, I had to change the url for idp_version (3.4.3) to reflect where 3.4.3 resides now. The new url is https://shibboleth.net/downloads/identity-provider/archive/$idp_version/shibboleth-identity-provider-$idp_version.tar.gz (archive is added). I added the 127.0.0.1 idptestbed.com to the /etc/hosts.
I executed sudo docker-compose up -d. The run was successful and I had port 8000 and 80 up.
Here is the error I get for http://localhost:8000
The webpage at http://localhost:8000/ might be temporarily down or it may have moved permanently to a new web address.
ERR_SOCKET_NOT_CONNECTED
Here is what I get for http://localhost:80Error 404 - Not Found.
No context on this server matched or handled this request.
Contexts known to this server are:
Context Path Display Name Status LifeCycle
/idp Shibboleth Identity Provider Not Available STARTED
icon Powered by Eclipse Jetty:// Server
I appreciate your help in resolving these issues.
Thanks
Emil
The text was updated successfully, but these errors were encountered: