API key group size pattern
Ruhrpottpatriot.7293:
I think this might be the case, but I’m not actually sure myself.
Do the api keys follow a certain pattern? For now I got 8-4-4-4-20-4-4-4-12 as size. Does this hold true for all generated keys, or are there deviations?
fro.8967:
The keys are always two GUIDs back-to-back. 72 characters total including dashes.
Lawton Campbell.8517:
We reserve the right to change the key format and/or length. Treat it as an opaque string no longer than 72 characters.
Would really like to see it be half the size, but there are annoying-to-remove technical restrictions that are currently keeping it long.
Ruhrpottpatriot.7293:
We reserve the right to change the key format and/or length.
This was somewhat clear to me. But even if the key format changes, I can assume that they will have a definitive format?
fro.8967:
As long as they stick with GUIDs, the pattern is always 8-4-4-4-12.
Ruhrpottpatriot.7293:
Lawton didn’t specify, that is will be a GUID pattern, nor did he specify how long they will be in the future, but that is not a concern of mine. I just want to know, if they will have a well defined format, whatever that might be.
StevenL.3761:
For now, this is the formal definition: 1 to 72 US-ASCII characters.
Lawton Campbell.8517:
For now, this is the formal definition: 1 to 72 US-ASCII characters.
^ This. I can’t even promise we’ll stick to GUIDs in the future, just that the string will never be longer than 72 characters.
Realistically, changing that piece is a lot of work for fairly little benefit, so it’ll probably be 2 concatenated GUIDs for a long time.