-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix JS regex use to validate IRIS IAM strings #354
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It feels like these should eventually not be hardcoded values.
Minor point but should It's probably obvious, but just to note that the commented out |
Seems like a good idea. |
Why was it not used in the first place, and what would be the implication of the 'give away'? |
From what I can recall, I think it was a combination of seeming unnecessary, and that I couldn't test it fully, as my instance of GOCDB didn't have IRIS IAM auth enabled (so I wasn't even registered myself). I think the longer form was essentially a placeholder based on discussions with @gregcorbett about the expected full form of the ID string, but later we moved towards more minimal validation that was sufficient to differentiate the different auth types (e.g.
I meant in the sense of helping people too much in guessing what an ID string should be that they're not in possession of, but I don't think it's really an issue? |
Ah yes, I've changed the code but not the comment 🤦 |
No I don't think so. The form is (needs to be) published info. I guess this validation is aimed at trapping typos in a form input field. |
cb56cf9
to
ef3d5da
Compare
I've fixed this and rebased (into a single commit) the branch on top of the latest dev. |
This has been running on the IRIS instance since at least Jun 2022. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
rebasing on latest dev |
Co-authored-by: ineilson <ian.neilson@stfc.ac.uk>
ef3d5da
to
927ede8
Compare
No description provided.