w and tested
> it. M2 is now available.
>
>
>
> *From:* cas-...@apereo.org [mailto:cas-...@apereo.org
> ] *On Behalf Of *John Stevens II
> *Sent:* Tuesday, June 21, 2016 11:09 AM
> *To:* CAS Community >
> *Cc:* mmoa...@unicon.net
> *Subject:* Re: [cas-user] Res
[mailto:cas-user@apereo.org] On Behalf Of John
Stevens II
Sent: Tuesday, June 21, 2016 11:09 AM
To: CAS Community
Cc: mmoay...@unicon.net
Subject: Re: [cas-user] Rest API Service Ticket Validation Issue
Misagh,
If the release date for version 5 is far off then I wouldn't mind doing the
> *To:* CAS Community >
> *Cc:* mmoa...@unicon.net
> *Subject:* Re: [cas-user] Rest API Service Ticket Validation Issue
>
>
>
> So I enabled oauth support but it looks like the user will be required to
> login via the GUI.
>
>
>
> I do see in
: [cas-user] Rest API Service Ticket Validation Issue
So I enabled oauth support but it looks like the user will be required to
login via the GUI.
I do see in the development branch (CAS OAuth Dev Link
<https://apereo.github.io/cas/development/installation/OAuth-OpenId-Authentication.h
t; *To:* CAS Community >
> *Cc:* mmoa...@unicon.net
> *Subject:* Re: [cas-user] Rest API Service Ticket Validation Issue
>
>
>
> My thinking is if I have developers who build API's and want to integrate
> CAS (not for sso but for centralized authentication) then a
lto:cas-...@apereo.org
> ] *On Behalf Of *John Stevens II
> *Sent:* Monday, June 20, 2016 7:04 AM
> *To:* CAS Community >
> *Cc:* mmoa...@unicon.net
> *Subject:* Re: [cas-user] Rest API Service Ticket Validation Issue
>
>
>
> My thinking is if I have developers who
cas-user@apereo.org
> ] *On Behalf Of *John Stevens II
> *Sent:* Monday, June 20, 2016 7:04 AM
> *To:* CAS Community >
> *Cc:* mmoa...@unicon.net
> *Subject:* Re: [cas-user] Rest API Service Ticket Validation Issue
>
> My thinking is if I have developers who build API'
ommunity mailto:cas-user@apereo.org>>
> Cc: mmoay...@unicon.net <mailto:mmoay...@unicon.net>
> Subject: Re: [cas-user] Rest API Service Ticket Validation Issue
>
> My thinking is if I have developers who build API's and want to integrate CAS
> (not for sso but for central
Sent: Monday, June 20, 2016 7:04 AM
To: CAS Community
Cc: mmoay...@unicon.net
Subject: Re: [cas-user] Rest API Service Ticket Validation Issue
My thinking is if I have developers who build API's and want to integrate
CAS (not for sso but for centralized authentication) then a user who want
ommended.
>>
>> On Friday, June 17, 2016 at 3:42:22 PM UTC-4, Misagh Moayyed wrote:
>>>
>>> /serviceValidate.
>>>
>>> *From:* cas-...@apereo.org [mailto:cas-...@apereo.org] *On Behalf Of *John
>>> Stevens II
>>> *Sent:* Friday, Jun
016 12:10 PM
To: CAS Community < cas-...@apereo.org >
Cc: jstev...@gmail.com ; dkopy...@unicon.net
Subject: Re: [cas-user] Rest API Service Ticket Validation Issue
Ok that may work, is that the recommended way to verify service tickets for
the Rest API (Without using the php client) or should I
Misagh Moayyed wrote:
>>
>> /serviceValidate.
>>
>>
>>
>> *From:* cas-...@apereo.org [mailto:cas-...@apereo.org] *On Behalf Of *John
>> Stevens II
>> *Sent:* Friday, June 17, 2016 12:10 PM
>> *To:* CAS Community
>> *Cc:* jstev...@gma
tevens II
> *Sent:* Friday, June 17, 2016 12:10 PM
> *To:* CAS Community >
> *Cc:* jstev...@gmail.com ; dkopy...@unicon.net
>
> *Subject:* Re: [cas-user] Rest API Service Ticket Validation Issue
>
>
>
> Ok that may work, is that the recommende
Misagh Moayyed wrote:
>
> /serviceValidate.
>
>
>
> *From:* cas-...@apereo.org [mailto:cas-...@apereo.org
> ] *On Behalf Of *John Stevens II
> *Sent:* Friday, June 17, 2016 12:10 PM
> *To:* CAS Community >
> *Cc:* jstev...@gmail.com ; dkopy...@unicon.net
> *Subject:*
/serviceValidate.
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of John
Stevens II
Sent: Friday, June 17, 2016 12:10 PM
To: CAS Community
Cc: jstevens...@gmail.com; dkopyle...@unicon.net
Subject: Re: [cas-user] Rest API Service Ticket Validation Issue
Ok that may work
Ok that may work, is that the recommended way to verify service tickets for
the Rest API (Without using the php client) or should I not be relying on
the actual client?
On Friday, June 17, 2016 at 2:49:08 PM UTC-4, Dmitriy Kopylenko wrote:
>
> By the time the /serviceValidate with ST is called,
Are you typing the requests (copy/paste)? If so, you may need to
increase the ticket expiration. ST expire in 10 seconds by default. Try
30 seconds.
See: bean id="serviceTicketExpirationPolicy"
Ray
On 2016-06-17 11:44, John Stevens II wrote:
> Need some insight on how to properly use the Rest AP
By the time the /serviceValidate with ST is called, the ST lifetime has expired
(10 seconds default). Increase the ST TTL on the CAS server to something
longer, but reasonable and see if it helps.
Best,
D.
> On Jun 17, 2016, at 2:44 PM, John Stevens II wrote:
>
> Need some insight on how to p
Need some insight on how to properly use the Rest API.
I have a simple php application below castest.php:
Visiting the php page in the browser works with no problem, I'm able to
authenticate and access the content with no problem.
I can post to my post server rest url to get my TGT:
Posting
19 matches
Mail list logo
