in 1) did you try with queryparameter TARGET={url of 2)}
2018-04-23 18:14 GMT-03:00 JON :
> It comes from a PrincipalBearingCredential generated in
> BasePrincipalFromNonInteractiveCredentialsAction
>
> TrustedAuthenticationConfiguration
>
>
>
> remoteUserAuthenticationAction
>
>
>
> BasePrincipa
It comes from a PrincipalBearingCredential generated in
BasePrincipalFromNonInteractiveCredentialsAction
TrustedAuthenticationConfiguration
remoteUserAuthenticationAction
BasePrincipalFromNonInteractiveCredentialsAction
The CAS page displayed to the user contains the following text:
"
So, to summarize, why is cas showing the error "Application not authorized"
when I am trying to go to url https://mycasserver/ws/idp/federation?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: h
check clients cas url
2018-04-23 16:19 GMT-03:00 Eric Knight :
> Any success figuring this out?
> I'm seeing the same thing.
> Eric.
>
> On Friday, February 12, 2016 at 6:33:20 AM UTC-8, Klaus wrote:
>>
>> We recently upgraded one of our Application Servers which formerly worked
>> perfectly toge
Any success figuring this out?
I'm seeing the same thing.
Eric.
On Friday, February 12, 2016 at 6:33:20 AM UTC-8, Klaus wrote:
>
> We recently upgraded one of our Application Servers which formerly worked
> perfectly together with our CAS Server. Now, after we upgraded that Tomcat
> Server it's
where comes user name in 4) from?
2018-04-23 13:32 GMT-03:00 JON :
> Thanks Manfredo
>
> Both work correctly
>
> Manually invoking the steps, the full flow works
>
> Theese are the steps I follow [all by browser]:
>
> 1.- I lunch the URL of a pac4j-saml client, that makes the SAML
> AuthnRequest
Hello All,
I'm having some trouble accessing my dashboard again and I'm fairly certain
it's an SSL cert error. I'm hoping to seek some help from this group.
Initially, I had a self generated cert that I created with the java keytool
and pointed it to my java ca-cert store. When trying to access
Viacheslav,
You will want to have handleLogoutRequests(true) so that logout is handled.
While testing, skip the CAS server array, just in case the network config
changes the apparent source of the request.
Put this in your CAS log4j2.xml to see what happens on CAS side of things:
Thanks Manfredo
Both work correctly
Manually invoking the steps, the full flow works
Theese are the steps I follow [all by browser]:
1.- I lunch the URL of a pac4j-saml client, that makes the SAML
AuthnRequest to the CAS SAML IdP (A)
2.- the browser is redirected by CAS, to the CAS login page
What protocol is the client using?
Attribute release is with SAML 1.1 or CAS 3.0 protocol.
See, https://apereo.github.io/cas/5.2.x/integration/Attribute-Release.html and
https://apereo.github.io/cas/5.2.x/protocol/Protocol-Overview.html.
Ray
On Sat, 2018-04-21 at 10:06 -0700, IOTech Co., Ltd wro
That's how phpCAS.log looks if i provide it with
phpCAS::handleLogoutRequests(false);
DA64 .=> phpCAS::client('S1', 'cas-1.server.test.pl', 443, '/cas')
[index.php:13]
DA64 .|=> CAS_Client::__construct('S1', false, 'cas-1.server.test.pl',
443, '/cas', true) [CAS.php:360]
DA64 .||Sta
Could you elaborate, please?
Quoting official documentation
at https://wiki.jasig.org/display/casc/phpcas+examples
"By default phpCAS by default only handles requests that emanate from the
CAS host exclusively (declared in phpCAS::client() or phpCAS::proxy()).
Failure to restrict SAML logout r
Test trusted and idp separately
El lunes, 23 de abril de 2018, JON escribió:
> Hi,
>
> I have the following running:
>
> cas-overlay-template-master 5.2.X with
>
>
>
> - SAML IdP
>
>
>
> - Trusted Authentication
>
>
>
>configured inside
>
>
> I must cover the following Single Sign-On federat
Logout requests are handled by clients.
.=> CAS_Client::handleLogoutRequests(true, array ( 0 => '
cas-1.server.test.pl',)) [CAS.php:1276]
D0EE .|Not a logout request [Client.php:1739]
See phpcas
El lunes, 23 de abril de 2018, Viacheslav Babanin
escribió:
> Hello, I have encountered issue
Hello, I have encountered issue with SSO for SAML 1.1 clients with CAS 5.2
I am rather new cas user and probably i am missing something obvious.
I am using folowing phpCAS client:
Advanced SAML 1.1 example
Advanced SAML 1.1 example
Authentication succeeded for user
.
User
Authentication flow ends BEFORE redirection (point 4 before 3)
El lunes, 23 de abril de 2018, JON escribió:
> Hi,
>
> I have the following running:
>
> cas-overlay-template-master 5.2.X with
>
>
>
> - SAML IdP
>
>
>
> - Trusted Authentication
>
>
>
>configured inside
>
>
> I must cover the f
Hi again
I think we'd better open another topic where better to expose the situation
this is the link
https://groups.google.com/a/apereo.org/forum/?hl=en#!topic/cas-user/jewd_Hzlens
Thank you very much, Manfredo and Ray
Jon
El jueves, 19 de abril de 2018, 21:12:48 (UTC+2), JON escribió:
>
>
Hi,
I have the following running:
cas-overlay-template-master 5.2.X with
- SAML IdP
- Trusted Authentication
configured inside
I must cover the following Single Sign-On federated flow:
1.- CAS SAML IdP (A), through the user's browser, receives a SAML
AuthnRequest in /cas/idp/pr
Ah, cryptography errors. My favorite. :-)
The problem here is that the server cannot validate the certification path
on some SSL certificate it's been given. Of course, Java being Java, the
error message isn't helpful enough to tell you which one. It could be its
own certificate, or it could be th
Yes Dave, I did.
But initially I had the entries in the json file i had already. But had to
move it to separate file as it was not reading the entry.
I got the login screen and when I entered the credentials as
casuser/Mellon, i see below error.
java.lang.RuntimeException: javax.net.ssl.SSLHan
20 matches
Mail list logo
