OAuth2 support

[Artyom Horuzhenko <ak...@gmail.com>]

Hello collegues,
I'm going to implement OAuth2 authorization support via various social
networks in OM 3.0. Users will be allowed to add their own servers. I'm not
sure how to keep information about OAuth2 servers: in db or xml file? First
way makes me to implement additional configuration UI for servers
management but it's more user friendly, second way is more easy. Does
anybody have and idea about best implementation way?

Re: OAuth2 support

[Artyom Horuzhenko <ak...@gmail.com>]

I could close access to it in web.xml


2013/8/5 Maxim Solodovnik <so...@gmail.com>

> I'm afraid XML file is not an option since it is downloadable and should
> not contain any credentials etc.
>
>
> On Mon, Aug 5, 2013 at 3:01 PM, Artyom Horuzhenko <akhor666@gmail.com
> >wrote:
>
> > Hello collegues,
> > I'm going to implement OAuth2 authorization support via various social
> > networks in OM 3.0. Users will be allowed to add their own servers. I'm
> not
> > sure how to keep information about OAuth2 servers: in db or xml file?
> First
> > way makes me to implement additional configuration UI for servers
> > management but it's more user friendly, second way is more easy. Does
> > anybody have and idea about best implementation way?
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>

Re: OAuth2 support

[Maxim Solodovnik <so...@gmail.com>]

I'm afraid XML file is not an option since it is downloadable and should
not contain any credentials etc.


On Mon, Aug 5, 2013 at 3:01 PM, Artyom Horuzhenko <ak...@gmail.com>wrote:

> Hello collegues,
> I'm going to implement OAuth2 authorization support via various social
> networks in OM 3.0. Users will be allowed to add their own servers. I'm not
> sure how to keep information about OAuth2 servers: in db or xml file? First
> way makes me to implement additional configuration UI for servers
> management but it's more user friendly, second way is more easy. Does
> anybody have and idea about best implementation way?
>



-- 
WBR
Maxim aka solomax