Mailing-List: contact user-help@oltu.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@oltu.apache.org
Received-SPF: pass (athena.apache.org: domain of lumus.sensus@gmail.com
 designates 209.85.128.194 as permitted sender)
MIME-Version: 1.0
Date: Mon, 18 Nov 2013 12:25:32 +0000
Message-ID: 
 <CALowLbHZ7g+Ln5-fhzYcc9x4BnUCQQ2wXzKFzYoxWsKzejSBRA@mail.gmail.com>
Subject: Oltu - getting started
From: Lumus Sensus <lumus.sensus@gmail.com>
To: user@oltu.apache.org
Content-Type: multipart/alternative; boundary=bcaec548a385ee0e4c04eb72a4f8

--bcaec548a385ee0e4c04eb72a4f8
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I am very interested in using this project for oauth, intially using the
authorization code grant and client credentials flows.

However, I'm a bit stuck on what exactly this project can do and am hoping
that someone can help.

I have some specific queries if anyone can answer any of them please:

1) Does the code provide an authorization server that authenticates the
resource owner? From what I can tell, there is an assumption that the RO
has already been authenticated and has an active session. Is there is also
an assumption that the AS is the same server as the resource server? If
this is the case, does the project provide any means to validate the access
token either on the RS or the RS making a call to the AS with the token (as
many oauth2 solutions are doing with a userinfo endpoint from OIDC)?

2) How is this project deployed? Is the parent project exported as a
library containing the sub-projects or does one build and deploy each
separate project depending on their needs? Any detail would be appreciated.

3) What in the project is stub code that needs to be completed and is there
guidance on how this might be done in the context of the API?

4) General guidance on what is provided and what is missing or intended to
be provided by the consumer of this project.

5) How does this project differ to the Spring OAuth2 framework?

I appreciate there are a lot of questions here, I can only offer that I
would be willing to update the documentation in way of thanks if I make
some progress.

Thanks,
Lumus

--bcaec548a385ee0e4c04eb72a4f8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<b=
r><br></div>I am very interested in using this project for oauth, intially =
using the authorization code grant and client credentials flows.<br><br></d=
iv>
However, I&#39;m a bit stuck on what exactly this project can do and am hop=
ing that someone can help. <br><br></div>I have some specific queries if an=
yone can answer any of them please:<br><br></div>1) Does the code provide a=
n authorization server that authenticates the resource owner? From what I c=
an tell, there is an assumption that the RO has already been authenticated =
and has an active session. Is there is also an assumption that the AS is th=
e same server as the resource server? If this is the case, does the project=
 provide any means to validate the access token either on the RS or the RS =
making a call to the AS with the token (as many oauth2 solutions are doing =
with a userinfo endpoint from OIDC)?<br>
<br></div>2) How is this project deployed? Is the parent project exported a=
s a library containing the sub-projects or does one build and deploy each s=
eparate project depending on their needs? Any detail would be appreciated.<=
br>
<br></div>3) What in the project is stub code that needs to be completed an=
d is there guidance on how this might be done in the context of the API?<br=
><br></div>4) General guidance on what is provided and what is missing or i=
ntended to be provided by the consumer of this project.<br>
<br></div>5) How does this project differ to the Spring OAuth2 framework?<b=
r><br></div><div>I appreciate there are a lot of questions here, I can only=
 offer that I would be willing to update the documentation in way of thanks=
 if I make some progress.<br>
</div><div><br></div>Thanks,<br></div>Lumus<br><div><div><div><div><br><div=
><div><br><br></div></div></div></div></div></div></div>

--bcaec548a385ee0e4c04eb72a4f8--