Release 0.5.0

[nivemaham]

Changes from release 0.4.1

MetaQR code #275

• Adds a new entity to store refresh-token for subjects and relevant meta-data.
• Send tokenUrl in oauth-pair response
• Add new resource to fetch meta-token
• Add privacy-policy-url and baseUrl to metaToken Add privacy policy url to metaQR code.  #297
• Share client secret with meta-token Meta token should contain client secret too #311 (Client secret no longer used for public OAuth clients, see links to discussions in Set OAuth client secret to empty for public OAuth clients #317)

Exception Harmonization #294

• We have new exceptions based on HTTP Status code conventions and a ExceptionTranslator to implement body and headers.

Other fixes

• Ignore exceptions during SourceTypeLoading Crash on radar-schemas 0.3.4 #291
• Add support for CONNECTOR types in SourceTypeLoader Add support to Connector type from catalog server #299
• Configurable admin password Admin password should be configurable via Environment variable #289
• Upgrade lodash dependencies.
• Fix NullPointerException during configLoading. YamlServerConfig throws NullPointerException on file not found #304
• Update logos and icons of radar-base.org. Update logos and icons of radarbase #292
• Add hasPermissionOnSource Add RadarToken.hasPermissionOnSource method #308
• Dockerfile build staging (Move to Staged Dockerfile #301)
• Update to the JWT signing code (Update signing code #315)
• Fix OAuth environment variable documentation
• Allow public OAuth clients to use authorization_code and refresh_token flows without the use of a client secret (Set OAuth client secret to empty for public OAuth clients #317).

Closes #275, closes #289, closes #291, closes #292, closes #294, closes #297, closes #299, closes #301, closes #304, closes #308, closes #311, closes #313, closes #317.

[blootsvoets]

With RADAR-base/RADAR-Docker#154, the sleep in the meta-qr code may not be needed at all. It should then still be documented in the readme that the at code should definitely be rate limited by upstream web servers.

It would still be good to document/modify the description in README.md of how OAuth2.0 clients should integrate with MP using the Meta-QR code

[blootsvoets]

LGTM