Developer Tools
Basic Auth Generator
Basic Auth Generator is part of Toolspire and is ready as soon as this page loads. The header is Basic, a space, then base64 of user, a colon, and the password. A colon inside the user name is rejected because it would split the pair.
On this page
What you can do here
The RFC example is the check
If the sample header differs, the colon or the space was lost.
User and password stay separate
You do not type the colon yourself.
Not a login
The page builds a header. It does not send it.
The sequence
How to use the Basic Auth Generator
- 1
Leave the sample and read the header
It should match the RFC string.
- 2
Replace both fields for your own pair
Do this on a machine you trust. The value is only base64.
- 3
Send it only over HTTPS
Anyone who sees the header can decode the password.
Worth knowing
- Basic Auth Generator on Toolspire: Aladdin and open sesame produce Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==.
- That base64 decodes to Aladdin:open sesame, which is the example in RFC 7617.
- A colon in the user is rejected. The colon is the separator.
- Characters outside Latin-1 are rejected, because btoa cannot encode them.
Base64 is not a secret
HTTP Basic credentials are the user, a colon and the password, then base64. Aladdin:open sesame encodes to QWxhZGRpbjpvcGVuIHNlc2FtZQ==. Anyone can decode that string. The header is useful as a standard, and it hides nothing from a person looking at the request. Use it on HTTPS, and do not treat the result as encrypted.
FAQ
Questions about Basic Auth Generator
Where does Basic Auth Generator run?
What header does Aladdin / open sesame produce?
Why reject a colon in the user name?
Is the password encrypted?
Will this log me in?
Keep going
Related tools
Last updated Report a problem or suggest a feature