Today I created a new organization and assigned 1 device to it and I also created an API key with read-only access.
I sent this API key to a client and then checked a few hours later and the device was unassigned and the key non-existent.
Not sure how to replicate this bug but it seems it could have something to do with the organization being created just before assigning devices/creating API keys.
Cheers,
Ben
1 Like
Hello @bsefton
Reading your problem, and based on the context, I think that by mentioning API Key
you really mean Token
, and in this case, Ubidots has 3 types of tokens:
-
Account tokens: which have all the permissions
-
Organization tokens: whose permissions can be customized through the
API roles
option.
-
Device tokens: which can only have permissions to send or retrieve data.
Based on that information, we would like to know what type of token you are referring to so we can make some tests and check your problem.
I look forward to your answer.
-Ăngela
Hi Ăngela,
Yes, sorry about that I was referring to the tokens. It was an organization token which I had created shortly after creating the organization.
I was able to copy the token and I later noticed it was gone upon rechecking the organization 5-10 minutes later.
Thanks for the quick response.
Cheers,
Ben
Hi @bsefton
Thanks for the clarification!
Is this still happening to you? Because I was trying to replicate this bug but I couldnât. In order to help you, can you please send me by direct message your username and the name of the organization with which this happens to you to be able to verify?
All the best,
Ăngela
Hi Ăngela,
I have just tried to replicate the problem but the token I created is still there.
I canât see an option to send private messages using the Ubidots community forum. Happy to send through my username and the Org name that had the issue in private.
Cheers,
Ben
1 Like