Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support SSO #6

Open
kevinlewis3 opened this issue Oct 26, 2018 · 5 comments
Open

Support SSO #6

kevinlewis3 opened this issue Oct 26, 2018 · 5 comments
Labels
can't fix This will not be worked on enhancement New feature or request needs server functionality Functionality not available on the server

Comments

@kevinlewis3
Copy link

Does this tool support Single Sign-On?
@dotdashhhh
Copy link

+1

@cyrusingraham cyrusingraham added the enhancement New feature or request label Nov 7, 2018
@macblazer
Copy link
Contributor

macblazer commented Nov 7, 2018 •
edited
Loading

The Jamf Pro Classic API that this utility uses does not support SSO. Until there is a Jamf Pro API that supports SSO, this will not be possible.

https://developer.jamf.com/documentation#authentication

@cyrusingraham cyrusingraham removed the enhancement New feature or request label Nov 7, 2018
@dannyhanes
Copy link

@kevinlewis3 If you have it enabled, you could always use the failover url.

@macblazer macblazer added needs server functionality Functionality not available on the server can't fix This will not be worked on labels May 6, 2020
@macblazer
Copy link
Contributor

Jamf Pro v10.35.0 supports bearer tokens for authentication to the API. This is closer to SSO, but not quite.

We could update PPPC Utility to use bearer tokens for all API access. This may need to be optional so older versions of Jamf Pro running on-prem could still be supported.

@macblazer macblazer added the enhancement New feature or request label Sep 30, 2022
@macblazer
Copy link
Contributor

Bearer token usage based on username/password was added with #113.

Jamf Pro v10.49.0 supports OAuth client credentials flow for authentication to acquire a bearer token. Another step closer to SSO, but still not quite. Client credentials flow will be implemented with #120.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
can't fix This will not be worked on enhancement New feature or request needs server functionality Functionality not available on the server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cyrusingraham @dannyhanes @macblazer @kevinlewis3 @dotdashhhh