I'm trying to setup a helm chart to easily deploy CAS

Currently, I have : 
- A docker image 
: https://gitlab.agglo-lepuyenvelay.fr/docker-images/apereo-cas
  It uses https://getcas.apereo.org/ui to compile last stable CAS with 
required modules
  At startup, it also retrieve config from a provided git repo

- A Helm chart 
: https://gitlab.agglo-lepuyenvelay.fr/helm-charts/georchestra/apereo-cas
  Deploy the previous docker image on a K8S cluster
  In the README, I provide some instructions on how to generate crypto keys

My objective is to have a CAS that provide OAuth2 login as a server.

CAS Version : 7.2.4

Installed modules : support-jpa-ticket-registry, 
support-json-service-registry, support-ldap, support-oauth-webflow, 
support-saml-idp, support-reports

CAS config & services : https://gitlab.agglo-lepuyenvelay.fr/-/snippets/1066

With this config, CAS start well, I can access the login page, but when my 
client app try to connect to 
: 
https://georchestra.sig.lepuy.local/cas/oauth2.0/authorize?response_type=code&client_id=georchestra-oauth2&state=<maybe-sensible>&redirect_uri=https://georchestra.sig.lepuy.local/login/oauth2/code/cas-oauth2

It stay loading and never have response from server, and it become the same 
thing for all CAS requests.

I have nothing in logs, so I don't know what happen. For what I tested 
connexions to database and LDAP are OK.

I tried a lot of config and tests, since days but nothing work.

Can someone help me to understand what I'm doing wrong ?

-- 
- Website: https://apereo.github.io/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/4ff8f97e-0bb4-4d8f-9fb4-24fe5f49c9a0n%40apereo.org.

Reply via email to