Skip to content
This repository has been archived by the owner on Jan 18, 2025. It is now read-only.

[Question] Why isn't ServiceAccount._generate_assertion public? #489

Closed
theacodes opened this issue Apr 7, 2016 · 6 comments
Closed

[Question] Why isn't ServiceAccount._generate_assertion public? #489

theacodes opened this issue Apr 7, 2016 · 6 comments

Comments

@theacodes
Copy link
Contributor

Seems like generating a JWT with a service account might become more important in the future. Can we have a first-class method for generating them?

@theacodes
Copy link
Contributor Author

@dhermes (friendly, low-priority) ping.

@dhermes
Copy link
Contributor

dhermes commented Apr 20, 2016

It's fine with me, though you can probably achieve what you want without exposing _generate_assertion.

I was able to make a scopeless prototype using the already public oauth2client.crypt.make_signed_jwt.

@theacodes
Copy link
Contributor Author

Oh yeah, it's possible, it's just not pretty. I'm writing a sample for a new product that uses JWTs to authenticate and I'd prefer to do it in one line rather than several. :)

(I'm lazy).

@dhermes
Copy link
Contributor

dhermes commented Apr 20, 2016

Are you volunteering to implement #252?

@theacodes
Copy link
Contributor Author

I'm being pre-empted by a high-priority task until the end of the month, so let's see. I'll close this since we have an open issue for it.

@dhermes
Copy link
Contributor

dhermes commented Apr 20, 2016

I wasn't suggesting you close it, but if the issue is that you want it for scopeless credentials, then yes we do have an issue for it already.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants