Hi,
first of all, please bear in mind that the suggested way to work with Syncope
deployments, when in need to customize / extend / adjust the default settings,
configurations and logic is via* Maven project*.
All other means - standalone, deb packages, Docker images, etc, - are fine
either for
Hi,
BTW, so HOW do we add those extensions (I think we would want both the SAML and
OIDC ones, and also the SCIM extension)?
Can they be added to an already-built Syncope instance, or do they have to only
be included when building a new Syncope instance?
Sorry for all the questions!
Jim
Ahh! I just noticed from Section 3.17 of the Syncope reference guide that we
need to include those extensions during our Syncope build. I will check on
doing that or having that done.
Jim
On Monday, May 18, 2020, 06:18:58 AM EDT, ohaya wrote:
I noted that the OIDC article that yo
I noted that the OIDC article that you linked was from 2018, so it seems that
that configuration should be available in Syncope 2.1.5?
Jim
On Monday, May 18, 2020, 06:12:40 AM EDT, ohaya wrote:
Hi Francesco,
Ah. Thanks.
We potentially might be able to leverage either of the appro
Hi Francesco,
Ah. Thanks.
We potentially might be able to leverage either of the approaches you mentioned:
- We are using Oracle OAM to protect Syncope, and we can configure the OAM to
cause a SAML assertion to Syncope in an HTTP header. I was looking at the
article you linked, but in our Syn
Hi Jim,
short answer: no, you cannot log into Syncope Console via the "simple"
REMOTE_USER header, as injected by a reverse-proxy as Apache HTTPD or NGINX.
Long answer follows.
When you log into Console, the credentials are used to obtain a valid JWT from
Core, which allow further REST calls; an
Hi,
I have been able to configure an Apache proxy in front of Syncope
(/syncope-console) running under Tomcat. I am using mod_ajp to connect the
Apache to the Tomcat that Syncope is running under and I configured an AJP
connector on that Tomcat. Also, I am able to pass a logged-in user ("admi
