- Enable multiple admin clients per CO.
- Accept from OA4MP server both a 200 and a 201 when creating a new OIDC client.
- Adopt version 2.0.0 of COmanage Registry OA4MP plugin cfg syntax that uses a single QDL file for LDAP claims instead of two QDL files.
- Add definition of cfg format versions.
- Increase the number of callback URLs to 50.
- Use different execution phases in cfg.
- Add Named Configurations for managing custom cfg and QDL.
- Use QDL for configuring claims from LDAP.
- Support requesting a public client.
- Enable configuration of LDAP search filter attribute.
- Include email address in client configuration.
- Stylistic changes necessary for use with COmanage Registry version 4.0.0.
- Update validation of the field used to track the CoGroup to which client management privileges are delegated to support COmanage Registry release 3.3.3.
- Enable management of refresh tokens.
- Enable management of the edu.uiuc.ncsa.myproxy.getcert scope.
- Display an informational notice when a LDAP claim mapping will override a standard OIDC or CILogon claim.
- Compare scope requests and LDAP claim mappings and display a dialogue if reconciliation needed.
- Do not allow the asterisk wildcard character in callback URLs.
- Detect if the comment returned by the server differs from that the plugin uses (no user visibility).
- Switch to using RFC 7591 and RFC 7592 compliant OA4MP API.
- Add the capability for the platform administrator to configure as part of the admin client a delegated group of people that will be allowed to manage OIDC clients.
- Enable private-use URI schemes for callback URLs.
- Fix highlighting of invalid callback URLs.
- Verify plugin and server representations of client are synchronized before edit view renders.
- Prevent browser asking to save LDAP bind password.
- Better logging of requests and responses to and from OA4MP server.
- Fixed issue where an OIDC client that had been edited outside of the plugin with a change in scope was not detected.
- Fix issue where editing an existing client that did not have LDAP to Claim Mappings led to the incorrect values for LDAP connections being set for the client after adding LDAP to Claim Mappings.