Page Comparison

...

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-76

  • CORS can be handled by

    Jira Legacy
    server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1907

  • Testbed incompatilibity is weird: when I print out the contents of the ServletContext in the initializer, I see web.xml contents from the testbed app (not idp.war’s web.xml)

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-61

  • Works and fairly well tested - need to finish unit testing though

  • Currently way too complicated to inject non-default metadata policies via file (multiple beans needed) - must be simplified

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-21

  • Can CLI really be compatible with the authenticated:true

  • No error handling yet - the successful output is currently TokenResponse JSON - should it be a velocity view instead

  • Unit testing need to be finished

• Ref: users-list discussion. Client secret expiration time is not currently exploited.

Ian

John

Marvin

Phil

Rod

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1909

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key GEN-311

  • Removing central-disabled profile from parent project (main only) for Friday night's builds.

  • Discuss: Add a -P check-m2 profile (again to main only) to assist with releases.

• Jira Legacy
  server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1914

  • Mostly removing things (good)

  • A chance to reconverge to our “standard” jetty base

...