Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Low
Description
In case there are some special characters in the application key of the application, the credentials may not synchronize with backend correctly.
It was identified in an application with the app ID containing curly braces, e.g. 576asdeds95-{}119
The ID is created in the System DB OK, but when it is synchronized with backend, the following error is thrown by the corresponding job:
URI::InvalidURIError: bad URI(is not URI?): "/internal/services/123456789/applications/576asdeds95-{}119/keys/"
The App Id should probably be URI-encoded by porta (or the pisoni gem), and URI-decoded by apisonator properly.
Alternatively, we can restrict special characters by adding validation on system (but probably that's not the best idea).
Another similar case happened to an application that has a whitespace in the App ID (as the last character). In this case probably it makes sense to either add a validation to NOT allow spaces in the App Id, or trim leading or trailing whitespaces.
Attachments
Issue Links
- is related to
-
THREESCALE-10762 Command from Configuration page cause apicast to return 403
- To Develop
-
THREESCALE-10761 Problem with special chars in application_id in utilization
- To Test (QE)
-
THREESCALE-10763 Application description can not be {NUMBER}_
- To Test (QE)
- links to
-
RHEA-2024:126110 Release of 3scale components for RHOAM - Containers
- mentioned on