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

Use OAuth and installation API to install Private apps into user accounts #10

Open
maximeprades opened this issue Aug 14, 2013 · 10 comments

Comments

@maximeprades
Copy link

@roseleaf
Copy link
Owner

roseleaf commented Oct 1, 2013

Actually probably not going to use OAuth. Doing so would require every single user to create an oauth client in their zendesk, authorize it, then use it in labs. Skip and I discussed this and feel that using the rails app to make api requests will be a much simpler user experience.

@maximeprades
Copy link
Author

I disagree. We should create a "public" OAuth client that can be used by All zendesk accounts, if you have an OAuth client I can turn it into a public one

@skipjac
Copy link
Collaborator

skipjac commented Oct 1, 2013

I agree with Rose.
On Oct 1, 2013 4:10 PM, "Maxime Prades" [email protected] wrote:

I disagree. We should create a "public" OAuth client that can be used by
All zendesk accounts, if you have an OAuth client I can turn it into a
public one


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-25500588
.

@maximeprades
Copy link
Author

If your biggest concern is "Doing so would require every single user to create an oauth client in their zendesk, authorize it, then use it in labs" and that I tell you I can lift that limitation, what are the blockers?

@skipjac
Copy link
Collaborator

skipjac commented Oct 2, 2013

At this point I don't see any value in using OATH and just see a lot of
hassles.

On Tue, Oct 1, 2013 at 4:28 PM, Maxime Prades [email protected]:

If your biggest concern is "Doing so would require every single user to
create an oauth client in their zendesk, authorize it, then use it in labs"
and that I tell you I can lift that limitation, what are the blockers?


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-25501550
.

@maximeprades
Copy link
Author

The security risk with a traditional API approach is big and the usability
is terrible

I might simply take it over and implement it with our resources if you guys
aren't willing to do it

Maxime Prades
Product Manager

Zendesk http://www.zendesk.com/
Mobile +1 (415) 623 8234 | Direct (415) 240-4690 http://+14152404690 |
Skype zendesk.maxime | Twitter @prades_maxime

On Wed, Oct 2, 2013 at 10:31 AM, Skip Moore [email protected]:

At this point I don't see any value in using OATH and just see a lot of
hassles.

On Tue, Oct 1, 2013 at 4:28 PM, Maxime Prades [email protected]:

If your biggest concern is "Doing so would require every single user to
create an oauth client in their zendesk, authorize it, then use it in
labs"
and that I tell you I can lift that limitation, what are the blockers?


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25501550>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-25504389
.

@roseleaf
Copy link
Owner

roseleaf commented Oct 2, 2013

I am totally with you Maxine if you're willing to work with me in making it
more user friendly to the end-users. Let's meet briefly next week about it.
My comment above was my main concern.

On Tue, Oct 1, 2013 at 5:34 PM, Maxime Prades [email protected]:

The security risk with a traditional API approach is big and the usability
is terrible

I might simply take it over and implement it with our resources if you
guys
aren't willing to do it

Maxime Prades
Product Manager

Zendesk http://www.zendesk.com/
Mobile +1 (415) 623 8234 | Direct (415) 240-4690 http://+14152404690 |
Skype zendesk.maxime | Twitter @prades_maxime

On Wed, Oct 2, 2013 at 10:31 AM, Skip Moore [email protected]:

At this point I don't see any value in using OATH and just see a lot of
hassles.

On Tue, Oct 1, 2013 at 4:28 PM, Maxime Prades [email protected]:

If your biggest concern is "Doing so would require every single user
to
create an oauth client in their zendesk, authorize it, then use it in
labs"
and that I tell you I can lift that limitation, what are the blockers?


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25501550>
.


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25504389>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-25504572
.

@maximeprades
Copy link
Author

And it's a comment that makes absolute sense but I can easily lift that
limitation by turning your client into a global one

The way I see it it's a great feature for zenlabs and a good engineering
challenge for you. If you guys don't do it I will, but obviously you have
deeper knowledge of Zenlabs so it'd be smarter if you guys owned it. I
can't make that call unfortunately so it will be Skip's and your decision
in the end...

On Wed, Oct 2, 2013 at 10:42 AM, Rose Auravide Trujillo <
[email protected]> wrote:

I am totally with you Maxine if you're willing to work with me in making
it
more user friendly to the end-users. Let's meet briefly next week about
it.
My comment above was my main concern.

On Tue, Oct 1, 2013 at 5:34 PM, Maxime Prades [email protected]:

The security risk with a traditional API approach is big and the
usability
is terrible

I might simply take it over and implement it with our resources if you
guys
aren't willing to do it

Maxime Prades
Product Manager

Zendesk http://www.zendesk.com/
Mobile +1 (415) 623 8234 | Direct (415) 240-4690 http://+14152404690
|
Skype zendesk.maxime | Twitter @prades_maxime

On Wed, Oct 2, 2013 at 10:31 AM, Skip Moore [email protected]:

At this point I don't see any value in using OATH and just see a lot
of
hassles.

On Tue, Oct 1, 2013 at 4:28 PM, Maxime Prades <
[email protected]>wrote:

If your biggest concern is "Doing so would require every single user
to
create an oauth client in their zendesk, authorize it, then use it
in
labs"
and that I tell you I can lift that limitation, what are the
blockers?


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25501550>

.


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25504389>
.


Reply to this email directly or view it on GitHub<
https://github.com/roseleaf/labs_beta/issues/10#issuecomment-25504572>
.


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-25504993
.

@roseleaf
Copy link
Owner

roseleaf commented Oct 2, 2013

Yeah. I like this idea.
I'm in Minneapolis right now but will look into it as well tonight and later

@roseleaf
Copy link
Owner

roseleaf commented Oct 2, 2013

Where's a reasonable place to make the OAuth client though? Or should I just start with a test account

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

No branches or pull requests

3 participants