Connect2id server 3.2
Version 3.2 of the Connect2id server for IdP and SSO based on the new OpenID Connect / OAuth 2.0 stacks introduces a few small tweaks under the hood.
-
Adds a default configuration template for setting up clustering on the AWS cloud with node discovery based on a shared S3 bucket.
-
Fine tunes the session store API to prevent accidental deletion of multiple sessions.
-
Dumps bits of the LDAP schema into the log on server startup to make it easier to troubleshoot LDAP directory issues.
-
Upgrades a number of packages, such as JAX-RS Jersey and Dropwizard Metrics to their latest stable versions.
For more information check the release notes below.
Download
To download a ZIP package of Connect2id server 3.2:
https://c2id-downloads.s3.eu-central-1.amazonaws.com/server/3.2/Connect2id-server.zip
As WAR only:
https://c2id-downloads.s3.eu-central-1.amazonaws.com/server/3.2/c2id.war
Questions?
Don’t hesitate to contact Connect2id support.
Connect2id Server 3.2 release notes
Configuration
- No changes
Web API
- Requires an all=true query parameter to delete all end-user sessions at the /session-store/rest/v2/sessions resource. Intended to prevent accidental deletion of all sessions.
Dependencies
-
Upgrades to com.nimbusds:oauth2-authz-store:3.0.5
-
Upgrades to com.nimbusds:oidc-session-store:2.1
-
Upgrades to com.nimbusds:common:1.90
-
Upgrades to com.unboundid:unboundid-ldapsdk:3.0.0
-
Upgrades to org.glassfish.jersey.containers:jersey-container-servlet:2.19
-
Upgrades to io.dropwizard.metrics:metrics-core:3.1.2
-
Upgrades to io.dropwizard.metrics:metrics-healthchecks:3.1.2
-
Upgrades to io.dropwizard.metrics:metrics-servlets:3.1.2
Other
-
Adds JGroups configuration template for S3-ping node discovery resources/default-jgroups-s3ping.xml
-
Logs LDAP schemas of required object classes on server startup to ease debugging.