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
adding support for SciTokens https://scitokens.org/ #69
Conversation
Thanks @ag012! I submitted a corresponding XSEDE activity for this feature at https://software.xsede.org/display/xci-694.
@@ -30,6 +30,7 @@ BuildRequires: libtool-ltdl-devel | |||
BuildRequires: checkpolicy | |||
BuildRequires: policycoreutils-python | |||
BuildRequires: python-setuptools | |||
BuildRequires: scitokens-cpp |
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.
The scitokens-cpp package can be built from source (https://github.com/scitokens/scitokens-cpp) or RPMs are available from OSG (https://opensciencegrid.org/docs/common/yum/) and soon from EPEL (https://src.fedoraproject.org/rpms/scitokens-cpp).
|
||
Payload format for Scitokens: | ||
"scope": “ssh:username", | ||
"aud": "demo.scitokens.org" |
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 think the audience (aud) is the hostname of the SSH server, based on the gethostname() call in scitoken_verify().
|
Note that rewrite _cmd_login 78f9c13 added a non-optional configuration field and it should be mentioned outside of the scitokens section in readme |
@jbasney this may be both overly pedantic and not be the right place to discuss this, but on the XSEDE activity the term "proprietary" seems inappropriate for Globus Auth OAuth 2.0 Tokens. They're opaque bearer tokens based on IETF RFC 7662. Opaque is not the same as proprietary. |
I'm happy to be corrected. It's my understanding that only tokens issued by globus.org are currently accepted by oauth-ssh, but I agree it should be possible to support any issuers of opaque bearer tokens that comply with RFC 7662 by adding a few new oauth-ssh configuration options. I opened issue #70 for it. In that case, I'd agree the term "proprietary" would no longer be appropriate. In any case, I removed "proprietary" from the description at https://software.xsede.org/display/xci-694. |
Thanks, Jim. I'll contribute to #70. Well, participate, at least. |
If this is ready approved and ready for merge, it'll need the 'draft' flag changed. |
No description provided.