Skip to content
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

Addding sentry & cas-oidc-provider as dependency #16

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

pmauduit
Copy link
Member

These are not needed per se, but:

  • the first one allows CAS to act as an OIDC provider, which could be useful if the SP is being replaced by the geOrchestra gateway but we still want to have our own identity provier.
  • The second one is sometimes used by Camptocamp deployments to be able to send some issues into a Sentry.io instance

These are not needed per se but:

* the first one allows CAS to act as an OIDC provider, which could
  be useful if the SP is being replaced by the geOrchestra gateway
  but we still want to have our own identity provier.
* The second one is sometimes used by Camptocamp deployments to
  be able to send some issues into a Sentry.io instance
@fvanderbiest fvanderbiest merged commit ec773f3 into master Nov 21, 2023
2 checks passed
@fvanderbiest fvanderbiest deleted the add-cas-oidc-provider-and-sentry branch November 21, 2023 12:26
@fvanderbiest
Copy link
Member

Thanks Pierre !

f-necas added a commit to georchestra/datadir that referenced this pull request Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants