Page Comparison

...

Attendees:

Done:

Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-78
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-79
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-81

Almost there:

Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-82
- It feels that we should simply disable the wiring of the secret expiration configuration and note it in the documentation
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-76
- I didn’t find a better way for “configuring” the ServletContextInitializer than via system properties
  - Flag for disabling the class:
    - -Dnet.shibboleth.idp.plugin.oidc.op.servlet.RegisterFilterServletContextInitializer=disabled
  - Space-separated list for the url-mappings of the filter:
    - "-Dnet.shibboleth.idp.plugin.oidc.op.servlet.RegisterFilterServletContextInitializer.mappings=/profile/oauth2/* /profile/oidc/*"
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-21
- CLI can handle HTTP-Basic auth - needed if the authenticated-flag is enabled in the admin flow config
- The flow now uses FetchThroughMetadataCache
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-61
- Configuration of additional server-side policies now simplified

m2 checking on by default
- Is this the correct default?
- -P central-disabled is no more
java-mvn-enforcer releases
- -data 1.0.2
Did the releases from docker with an ssh tunnel.
- Are we good to turn off external access?
The bug in maven which required us to turn off checksum checking on our repos has been fixed.

...