Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 25 Jan 2013 10:53:14 +0000 (UTC)
From: "Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12628691.1358852537500.190497.1359111194665@arcas>
In-Reply-To: <JIRA.12628691.1358852537500@arcas>
References: <JIRA.12628691.1358852537500@arcas>
Subject: [jira] [Commented] (FEDIZ-48) Support wfresh properly in the IdP
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/FEDIZ-48?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D135625=
95#comment-13562595 ]=20

Colm O hEigeartaigh commented on FEDIZ-48:
------------------------------------------

Hi Oli,

I'm a bit confused by the definition in the spec:

> An IP/STS SHOULD NOT issue a token with a longer lifetime.  If specified =
as =E2=80=9C0=E2=80=9D it indicates a request for > the IP/STS to re-prompt=
 the user for authentication before issuing the token.

So if the RP passes "wfresh=3D0", what should the subsequent Expiry date of=
 the STS issued token be? According to the above it should not be longer th=
an the given value of wfresh.

Colm.
               =20
> Support wfresh properly in the IdP
> ----------------------------------
>
>                 Key: FEDIZ-48
>                 URL: https://issues.apache.org/jira/browse/FEDIZ-48
>             Project: CXF-Fediz
>          Issue Type: Improvement
>    Affects Versions: 1.0.2
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 1.1.0, 1.0.3
>
>
> This task is to properly support wfresh in the IdP. Currently, we only su=
pport "wfresh" in the context of forcing a re-authentication if it's equal =
to "0". We should also use it to specify the Lifetime when requesting a tok=
en from the STS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira