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.

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

Support Private and Public applications #1

Open
judgej opened this issue Apr 4, 2019 · 1 comment
Open

Support Private and Public applications #1

judgej opened this issue Apr 4, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@judgej
Copy link
Member

judgej commented Apr 4, 2019

These have different configuration items and different algorithms.

@judgej judgej added the enhancement New feature or request label Apr 4, 2019
@judgej judgej self-assigned this Apr 4, 2019
@judgej
Copy link
Member Author

judgej commented Apr 15, 2019

  • Private apps allow access to a single named organisation, do not expire, and do not require a callback URL. Great for developing an application against, as they can be developed from any location and on any type of hosting.
  • Public apps allow authorisation against any organisation, which lasts for half an hour, but requires a single fixed callback URL. This is good for UAT or small production apps that do not need unattended access to an organisation.
  • Partner apps allow access any organisation, and tokens can be continually renewed, so the app has unattended access once authorised. Up to three callback domains can be set up, so the callback is a lot more flexible. This flexibility comes at a higher price to provision as a higher level of trust is needed.

Private app support would be good next, for development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant