FIX-2180 Credentials

[eliasbruvik]

Fixes

This pull request fixes #2180

Description

Added support for using shared credentials across multiple witsml servers when using oAuth with azure.

• Added a Credential Ids input when editing a server. Only people with the admin role will be able to edit this when oAuth is enabled.
• Added CredentialIds to the server objects. This is stored along with the rest of the server object in the database.
• Added CredentialId to ServerCredentials. This will be populated with from the name of the keyvault secret. For example sharedCredentials from the secret with name witsmlcreds--sharedCredentials--Host
• When looking for system credentials for a server, if CredentialIds is specified, it will match the credentialIds to find the credentials. If it is not specified, it will use the Uri. This way you don't have to make any changes in the application or the keyvault after this PR has been merged.
• Everything keeps the same format in the keyvault, so old versions of witsml explorer will not be affected.

Testing these changes can be a bit difficult unless you are using oAuth with system-user secrets in Azure. I have tested it as thorough as possible (with oAuth), but I only had one system user to test it on.

NOTE: If you "degrade" from these changes to one without CredentialIds, the CredentialIds field might have to be removed from the database.

If you are reviewing this PR, please use some time to think about if I have managed to keep the credentials secure. You still need to have the admin role to change CredentialIds, and you still need to have a role that overlaps with the server roles in order to actually use the credentials.

Type of change

• Bugfix
• New feature (non-breaking change which adds functionality)
• Enhancement of existing functionality
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Impacted Areas in Application

• Frontend
• API
• WITSML
• Other (please describe)

Checklist:

Communication

• I have made corresponding changes to the documentation
• PR affects application security

Code quality

• I have self-reviewed my code
• No new warnings are generated

Test coverage

• New code is covered by passing tests

Further comments

[janmarius]

Reviewer checklist

• Read issue and PR
• Pulled branch and manually tested
• Verify that PR resolves issue
• Reviewed the code