-
Notifications
You must be signed in to change notification settings - Fork 108
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
Remove hyphen from openid-connect section of the endpoints api #3241
Remove hyphen from openid-connect section of the endpoints api #3241
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.
I don't know that issuer
needed to change to server
(although I suspect it's more accurate as we have the broker address but we expect an different SSO "issuer") ... but I don't object. 😄
By the way; make sure your merge commit has a better explanation than just that. |
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.
👍
I updated the description with a commit message. |
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.
Why is this needed?
I'm sorry that the references in the description weren't sufficient. The answer is that the presence of the hyphen in the name, |
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.
Is this the kind of code change we want to be making now before we have verified the server is deployed in staging? It seems that given our time constraints to deploy by mid-March we should spend on time on other kinds of changes.
@@ -140,15 +140,15 @@ def check_config(self, client, server_config, host, my_headers={}): | |||
|
|||
try: | |||
oidc_client = server_config.get("openid-connect", "client") |
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.
FWIW, these lists were in sorted order.
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.
I support keeping the list in sorted order.
On another note, @portante, when commenting on multiple lines, you can drag-select to highlight the range, and doing so has two effects: first, in the "Conversation" display, your comment will be preceded by the code from the range (instead of the default three or so lines), and, second and more importantly, your comment will be displayed after the range (in this instance, it would have made clear what you meant by "these lists").
except (NoOptionError, NoSectionError): | ||
pass | ||
else: | ||
endpoints["openid-connect"] = { | ||
endpoints["openid"] = { |
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.
Perhaps "OpenID Connect" could be shortened to oidc
if we really need it that short?
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.
Brevity is not the issue; what we're trying to do is to make it be a valid Javascript identifier, which means removing the hyphen.
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.
Is this the kind of code change we want to be making now before we have verified the server is deployed in staging? It seems that given our time constraints to deploy by mid-March we should spend on time on other kinds of changes.
That question is constructive looking forward; however, as regards this particular change, the work is already done, and I do not think that accepting this change at this point will adversely affect the Staging server deployment (and, I believe that it will ease the addition of Keycloak-based authentication).
@@ -140,15 +140,15 @@ def check_config(self, client, server_config, host, my_headers={}): | |||
|
|||
try: | |||
oidc_client = server_config.get("openid-connect", "client") |
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.
I support keeping the list in sorted order.
On another note, @portante, when commenting on multiple lines, you can drag-select to highlight the range, and doing so has two effects: first, in the "Conversation" display, your comment will be preceded by the code from the range (instead of the default three or so lines), and, second and more importantly, your comment will be displayed after the range (in this instance, it would have made clear what you meant by "these lists").
except (NoOptionError, NoSectionError): | ||
pass | ||
else: | ||
endpoints["openid-connect"] = { | ||
endpoints["openid"] = { |
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.
Brevity is not the issue; what we're trying to do is to make it be a valid Javascript identifier, which means removing the hyphen.
I don't believe the principle of accepting something because it is already done is a good principle to follow for a project. That line of thinking means that any PR submitted should be accepted because it is done. In this case, we don't need to be accepting ANYTHING for OpenID Connect support. If folks want to build up a series of commits for OpenID Connect on a separate branch to be merged later, great. But we need to remain focused. |
@portante If you want to have |
FWIW, this will now land in |
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.
👍
Since this is no longer targeting main
it is not a concern.
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
…ibuted-system-analysis#3241) Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
Remove hyphen from openid-connect section of the endpoints API - Getting rid of the excess quotes and brackets would make this easier to read - It also makes it easier to reference in Dashboard javascript code when there is no hyphen involved (endpoints.openid instead of endpoints['openid-connect'])
Addresses issue #3240
Originally asked here
Commit message:
Remove hyphen from openid-connect section of the endpoints API
no hyphen involved (
endpoints.openid
instead ofendpoints['openid-connect']
)