When managing web connections in FME Form and creating a new Token Service (OAuth 2.0 Credentials Flow) we need the possibility to base64 encode the consumerKey and consumerSecret in the header according to the following pattern: "Authorization: Basic <base64 encoded consumerKey:consumerSecret value>"
The current workaround is to bas64 encode the requested information with the TextEncoder transformer and then hard code the encoded value(s) in the web connection template which isn’t that generic.
