Device Registries do not accept credentials with auth-id containing underscore
See original GitHub issueThe Device Registry Management API defines the authentication identifier pattern as [a-zA-Z0-9-_=.]+
which includes the underscore character. However, the registry implementations do not accept 4711_authid
as an authentication identifier.
So, either the pattern in the API needs to be changed to exclude the underscore or the implementations need to be changed to accept the underscore.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
FlutterFire_UI/Auth Email validation fails on '_' (underscore)
Attempt to register an email with an '_' fails: xxxx_xxxx@somewhere.com Not sure if this is in the firebase_auth package or _ui package.
Read more >Solved: Can't sign into VCSA with AD credentials
Run shell to activate the bash shell. Remove the vCenter Server Appliance from the domain by running this command: /opt/likewise/bin/domainjoin-cli leave
Read more >Panorama > Device Registration Auth Key - Palo Alto Networks
Name of the device registration auth key. The name is case-sensitive, must be unique across the entire device group hierarchy, and can contain...
Read more >Azure Machine Learning Python - Workspace Class
Defines an Azure Machine Learning resource for managing training and deployment artifacts. A Workspace is a fundamental resource for machine learning in ...
Read more >Configuring a credential strength policy - Google Cloud
A key element to the trust evaluation process is the strength of the user's login credentials, where access to specific types of applications...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I probably have removed the underscore in the implementation because I saw a couple of REST API designs guides that advised against using underscore in resources that where accessible through a URL. The argument being that it may cause confusion when linking such a resource, because the usual underline of URL resources may “hide” the underscore and someone could mistake it for a space.
IIRC we discussed it afterwards and chose to ignore that, and i probably failed to update the implementation. I am fine sticking to the spec if you guys also think the issue mentioned above is not a big deal.
closed via #2177