[go-nuts] [ANN] OSINCLI, OAuth2 client library

Eric Gavaletz

at Sep 20, 2013 at 10:53 pm

While working on

https://code.google.com/p/goauth2/

it was said that many providers don't implement the spec correctly. Have
you run into that problem developing one package to rule them all? Which
providers have you tested your client against? If you didn't run into
problems it would be interesting to look into what would make goauth2 more
complete since I am told it has a fairly large user base.

On Friday, September 20, 2013 3:42:07 PM UTC-4, Rangel Reale wrote:

Complementing my OSIN OAuth2 server library, I created a client library on
the same base.
It aims to be a complete implementation, and not tied to just one
provider, so it supports various configurations to be compatible with every
possibility. By default, it follows the RFC spec.

https://github.com/RangelReale/osincli

Thanks,
Rangel Reale

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

reply | permalink

Rangel Reale

at Sep 30, 2013 at 2:06 pm

⇧

For now only tested with Google and my OSIN library, but the most common
differences are covered by these options:

ErrorsInStatusCode bool
SendClientSecretInParams bool
UseGetAccessRequest bool

On Friday, 20 September 2013 19:53:07 UTC-3, Eric Gavaletz wrote:

While working on

https://code.google.com/p/goauth2/

it was said that many providers don't implement the spec correctly. Have
you run into that problem developing one package to rule them all? Which
providers have you tested your client against? If you didn't run into
problems it would be interesting to look into what would make goauth2 more
complete since I am told it has a fairly large user base.

On Friday, September 20, 2013 3:42:07 PM UTC-4, Rangel Reale wrote:

Complementing my OSIN OAuth2 server library, I created a client library
on the same base.
It aims to be a complete implementation, and not tied to just one
provider, so it supports various configurations to be compatible with every
possibility. By default, it follows the RFC spec.

https://github.com/RangelReale/osincli

Thanks,
Rangel Reale

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

reply | permalink

Ingo Oeser

at Sep 30, 2013 at 10:01 pm

⇧

On Friday, September 20, 2013 9:42:07 PM UTC+2, Rangel Reale wrote:

Complementing my OSIN OAuth2 server library, I created a client library on
the same base.
It aims to be a complete implementation, and not tied to just one
provider, so it supports various configurations to be compatible with every
possibility. By default, it follows the RFC spec.

https://github.com/RangelReale/osincli

Developing it without a single foo_test.go is very brave...
May I suggest adding some tests?

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

reply | permalink

group	golang-nuts @
categories	go
posted	Sep 20, '13 at 7:42p
active	Sep 30, '13 at 10:01p
posts	4
users	3
website	golang.org

responses	expanded	Hotkey: s
font	variable	Hotkey: f
user style	avatars	Hotkey: a

[go-nuts] [ANN] OSINCLI, OAuth2 client library

Search Discussions

Related Discussions

3 users in discussion