...
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-315 Currently marked for 4.2. I don’t recall the background on this. Do we still need to do?
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-344 Currently marked for 4.2. Is this just a simple exclude? There’s some discussion about doing things with Rod’s new checking support, etc.
...
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
...