Hello,
Currently, *LdapAuthenticationHandler.java* is handling the Ldap
authentication related to CAS. Suppose, I want to take some more operations
based on the result of the Ldap authentication, how I be able to do the
same? I mean something extra like locking the user, if the user tried
Hello,
How to establish connection between java window client and
cas server of ubuntu.
Thanks & Regards
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
Ray,
No, i need to know it on another application that is being SSO’ed to ie kinda
like an attribute
I’ll put some thought to a different approach.
Be well
Colin
> On Dec 4, 2020, at 3:59 PM, Ray Bon wrote:
>
>
> Colin,
>
> The audit log writes the service being accessed; when a ST is
Colin,
The audit log writes the service being accessed; when a ST is issued and when
validated.
Ray
On Fri, 2020-12-04 at 16:01 -0500, Colin Ryan wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive
Folks,
Is there a way to interrogate a ticket/session to get the original entry
point to the CAS SSO.
If have multiple entry points (services) to CAS, this get's thrown over
to CAS for validation/auth etc.
Then I visit another site on the same domain that is enabled for SSO
with the CAS
On a hunch, I tried turning on the attribute caching in the service entry and
it fixed the immediate issue.
This still leaves me a little puzzled. The documentation implies that the
principal should have been cached with the length of the default SSO session.
Time to keep digging.
From:
The usual "expire when the browser is closed".
On Wednesday, December 2, 2020 at 5:31:12 PM UTC-5 Ray Bon wrote:
> Dave,
>
> What is the expiry time on the TGC in your browser?
>
> Ray
>
> On Wed, 2020-12-02 at 14:25 -0800, Dave Steiner wrote:
>
> Notice: This message was sent from outside the
Robert,
Two different steps, two different configurations. Attributes for access may be
different from attributes the service needs/wants.
See, https://apereo.github.io/cas/6.2.x/integration/Attribute-Release.html, in
particular, attribute release policy.
Ray
On Fri, 2020-12-04 at 18:07
CAS 6.1 server
LDAP authentication + built in principal resolution
I am running into what I think is an inexperience issue with service access
strategies. I am attempting to use principal attributes to grant access to a
service.
Service entry:
{
"@class" :
I believe that it is serialized Java classes. So it's binary data. You
don't change it without an external service. I guess you could find the
code that does it and write you own service. But you don't be doing it
via direct DB manipulation.
On Fri, 2020-12-04 at 09:48 +, Francisco
Thanks, David, for the reassurance that it should be possible. I think we
found our config mistake.
On Tuesday, December 1, 2020 at 8:44:31 PM UTC-6 dhawes wrote:
> On Tue, 1 Dec 2020 at 15:22, Bryan K. Walton wrote:
> > Is it possible to use an If Statement like this to make CAS auth
> >
Hi everyone,
I can't figure out how can I determine accessStrategies and stuff through
the JPA service manager in version 6.2(.4). I have all the automatically
generated tables, but I cant seem to understand what goes into the LONGBLOB
columns.
How can I modify these parameters with or without
Hi all,
I encountered the same issue, and want to chime in with some additional
info:
I found that starting from CAS 6.2.x by default attributes from JDBC / LDAP
/ other PersonDirecotry are not by default released.
See this line
here:
13 matches
Mail list logo
