[OPENAM-13812] How to treat special character '$' in Amster/Rest Created: 18/Oct/18  Updated: 15/Nov/18  Resolved: 15/Nov/18

Status: Resolved
Project: OpenAM
Component/s: documentation
Affects Version/s: None
Fix Version/s: 6.0.0, 6.5.0

Type: New Feature Priority: Minor
Reporter: Jobby Thomas Assignee: Cristina Herraz
Resolution: Fixed Votes: 0
Labels: AME, SHAKESPEARE, rest
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Support Ticket IDs:


Problem Description:

Customer is trying to run an import-config command to import an OAuth2Client. Customer have templatized all their passwords and so also the client_secret of this client.
The client secret of this OAuth2Client is Pa$$w0rd111.

The load takes places properly via Amster. The import, however, poses a problem.


Amster 5.1.1



since $ is reserved it has be treated as the following

  1. after doing the following in the secret amster file cat secrets.amster oidc_client_api_portal='Pa\\$
    $w0rd111', the import went through
  2. the single ' and "
    " helped pass the import with $


next action:

it will be great in our amster document in how to treat special character as such

Comment by Cristina Herraz [ 15/Nov/18 ]

Note: Keep Dom updated about this Jira.

Note2: Amster limitations about escaping characters are Groovy's.

Using single quotes for strings as in the example means you cannot use variables inside the string, which is a problem with configuration expressions. So careful there. Wonder if slashy strings would work. Something like "/pa$$word/" ? Ofc this would not work if there are also / characters inside.

Moral of the story is, depending on the special characters, customers need to read Groovy's docs.

Comment by Cristina Herraz [ 15/Nov/18 ]

Added a mention about this in the import section.

Generated at Tue Nov 24 20:44:15 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.