Fix OutOfBound exception in ApiKey authentication Rest API #3177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an OutOfBound exception caused by too short ApiKey credential when using the Rest APIs. Moreover, the stacktrace produced by an exception in the ApiKey authentication step is now hidden to the final user, and a clearer message is logged.
Related Issue
n/a
Description of the solution adopted
The issue was caused by the length of the API key. If the API key was shorter than
KapuaAuthenticationSettingKeys.AUTHENTICATION_CREDENTIAL_APIKEY_PRE_LENGTH
(which is set by default to 8), thesubstring
method failed, because such length was shorter that theendIndex
parameter. Since it is not possible to have an API key that is shorter thanAUTHENTICATION_CREDENTIAL_APIKEY_PRE_LENGTH
, thefindByApiKey
now will fail in this case.Screenshots
n/a
Any side note on the changes made
n/a