Open mooreds opened 4 years ago
We don't ship any API keys - to use this test, you'll need to add that API key to FusionAuth, or modify the test locally to the API key you have configured.
It is an older "style" - we used to just generated UIIDs. But api keys a free form, they could be bob
or fred
if you want. :-) That would be a bad API key.
I think the test will also support reading the API key from environment variable if you prefer that method.
Did you want to change something about this? We could document better how to run the tests, add a comment to say change this to whatever your API key is - ideally we would not have people changing that value and checking it in - because it would just keep changing.
In this file:
https://github.com/FusionAuth/fusionauth-netcore-client/blob/master/fusionauth-netcore-client-test/fusionauth-netcore-client-test/test/io/fusionauth/Example.cs
The
apiKey
is6b87a398-39f2-4692-927b-13188a81a9a3
.This doesn't look like any of the API keys I've seen from FusionAuth 1.15, maybe it's an older style?
I found it confusing.