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

[maximeprades]

OAuth: https://support.zendesk.com/entries/24458591-Using-OAuth-authentication-with-your-application

Apps API: http://developer.zendesk.com/documentation/apps/reference/api.html

[roseleaf]

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]

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]

I agree with Rose.
On Oct 1, 2013 4:10 PM, "Maxime Prades" notifications@github.com 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]

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]

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 notifications@github.comwrote:

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]

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 notifications@github.comwrote:

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 notifications@github.comwrote:

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]

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 notifications@github.comwrote:

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 notifications@github.comwrote:

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 notifications@github.comwrote:

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]

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 <
notifications@github.com> 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 notifications@github.comwrote:

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 notifications@github.comwrote:

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 <
notifications@github.com>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]

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

[roseleaf]

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