The strict_encode64 is being used instead of encode64 since "\n" was present based on longer usernames, ie. "clintonskitson@email.com@guid-asdsaasd-asdasdasdas. I believe it is 60 characters that encode64 starts adding line breaks.
The post also had to be modified since headers were being added to the authorization parameter.
The strict_encode64 is being used instead of encode64 since "\n" was present based on longer usernames, ie. "clintonskitson@email.com@guid-asdsaasd-asdasdasdas. I believe it is 60 characters that encode64 starts adding line breaks.
The post also had to be modified since headers were being added to the authorization parameter.