Filesystem:

We support utf-8 names all characters so we should continue to allow these type of user names. We'll fix this in Console for right path decoding.

It looks like the / characters inside is breaking the path building, but I can be wrong

The actual problem is that base64 encoding is used to encode the username, but standard base64 encoding is not URL-safe (standard base64 encoding uses the + and / characters). To use URL-safe encoding, you should use base64.URLEncoding instead of base64.StdEncoding (RFC 4648). It's almost the same, but instead of the +/ characters, the URL-safe version uses -_.

However, it's not needed to encode the parameters, because Javascript already provides the encodeURIComponent(...) function to encode text. The advantage is that the Go server automatically decodes the parameters without needing to call any functions. Another advantage is that URLs look better (especially if they don't have any encoded characters).

It's a bit strange that the Swagger code generator doesn't perform this encoding, because it's the only sane thing to do. I'm not the only one who's wondering why that's not the default. Fortunately, it can be fixed with a hook that will automatically add this:

module.exports = {
    hooks: {
        onInsertPathParam: (paramName) => `encodeURIComponent(${paramName})`,
    }
};

That way, we don't need to bother which parameters need to be encoded and who don't need it. If they are passed on the URL (via this API module), then encoding is done automatically. If values are passed in the HTTP body (encoded as JSON), then no encoding is required. I have tested this method and it works fine. It does require to refactor all code and to remove the calls to encodeURLString and decodeURLString (unless in places where URLs are created in code).

To fix the issue for now I fixed the encodeURLString and decodeURLString methods to use URL-safe base64 encoding and also fixing the Go server. This fixes the issue and chance of breaking functionality is relative low.

I guess we need to go for the proper option in the long-term to reduce the chances of coding issues. This simplifies code and improves code quality and reliability (in the long-term).