-
Notifications
You must be signed in to change notification settings - Fork 88
How to get started #17
Comments
|
Thanks for your reply. I gather what I've experienced is not the regular behaviour and I should rather get a response when I've set up a minimal example: https://github.com/fiedl/cas-docker-test
The output is quite short and does not show any indication that the server is listening at port 8080.
Docker shows that the ports are correctly redirected.
Curl does not reach the server.
|
Could I assume that you have correctly created a keystore and CAS is using it? Because your logs seem incomplete. You should be seeing a READY asciiart, and since you dont that means something has gone wrong and the server has not really started. |
Actually, ignore the comment about the READY asciiart. That does not apply to 5.1.x, but the rest is all the same. Does port 8443 work? |
Also it appears that port 8080 is not by default enabled: You'll need to enable the port for the embedded tomcat first before you can access/expose it. |
@mmoayyed Thanks for the pointers, but I'm really not sure how to approach this. I'm still reading the CAS documentation. Maybe I did not understand this docker image altogether: I'm wondering if it is possible to use this docker image and configure it to connect to our ldap server, and maybe, also include a custom logo or welcome text, without coding any java, just by setting environment variables, mounting configuration files and resource folders through docker. |
I'm running into (I think) the same thing - I mapped port 8080 with -p8080:8080, and traffic is getting to Tomcat because it's showing up in the Tomcat access log, but I'm getting back 400 (Bad Request) when I try to navigate to the root of the site (http://localhost:8080) I haven't been able to find any configuration RE Tomcat at all. If there's something that needs to be enabled, I'm completely lost. |
Did someone find a solution ? I have the same issue... |
Yes and no. I never got the HTTP endpoint to work, but if I recall
correctly, I got the HTTPS endpoint to work from inside the container by..I
think generating a new cert, but it's been a while.
…On Fri, Mar 2, 2018 at 12:27 PM, sebastiennoir ***@***.***> wrote:
Did someone find a solution ? I have the same issue...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACPsRy91I0FNvZ573tNM368AqYDNleG7ks5taYDqgaJpZM4PPq1e>
.
|
I have the same problem, generate the certs, put in the keystore and the cacerts file, but still not working. Now my error is: |
I have the same problem too. |
Finally, I found the problem, the see more on |
I'm trying setup CAS as authentication proxy for several web applications.
Why opening an issue here?
Through the Getting Started Guide I got to the Docker Installation Guide, which, for instructions on the configuration, directs to this repo.
How to get started?
I've successfully created a docker container for
cas:v5.1.2
. Although the guide readsopeneing the ports suggested by
docker ps
in the browser does not work. Alsocurl
returns "curl: (52) Empty reply from server".Thus, I guess I'm missing some documentation on how to proceed. Could you give me some pointers on the following topics or point me to the corresponding documentation:
nginx
to redirect properly to CAS when authentication is needed.The text was updated successfully, but these errors were encountered: