[cas-user] UI customization in overlay
Hi all, I'm trying to customize the CAS css styles, using the maven overlay method. We used to overwrite the compiled css files in the overlay, but upgrading from 5.2 to 5.3 it seems far easier to change the sass templates that CAS provides. As far as I understand though, normally, no sass compilation takes place when building CAS with the overlay. Can anyone give a hint how to include sass compilation in the overlay build process? Or do you follow completely different paths customizing the UI? Regards, Arnold -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/39d9f71dfcf74c1b9e14171480c24211%40hrz.tu-darmstadt.de. smime.p7s Description: S/MIME cryptographic signature
[cas-user] remember me use
Hello, We have migrate from 4.2 to 5.2. Our need is simple, but we can't implement it . We put the option "remember me", with a delay of 6 months ( about). But even following the documentation, it is impossible to have a session maintained for more than a few hours by checking the "remember me" box. i try so many configuration... my last configuration is : cas.tgc.rememberMeMaxAge=1209600 cas.ticket.tgt.timeToKillInSeconds=172800 cas.ticket.tgt.maxTimeToLiveInSeconds=135 cas.ticket.tgt.timeout.maxTimeToLiveInSeconds=135 cas.ticket.tgt.rememberMe.enabled=true cas.ticket.tgt.rememberMe.timeToKillInSeconds=135 did anyone manage to make it happen: when you check "remember me" to have a session maintained for XX months when you do not check "remember me" with the session that closes at the end of the browser with a maximum time of XX hours. I'd be very interested! Best 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 --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/305a3ba8-d8ae-494c-bb20-df758bd2e0b0%40apereo.org.
[cas-user] Re: [Cas 5.1.8] Unable to connect to Database for authentication.
Hi Andy,
Thanks, for the reply.
I saw that link, but is there any example to implement the encoding and
configuring it in the application.properties.
Thanks,
Pandu Ranga T.
On Saturday, 25 August 2018 18:32:28 UTC+5:30, Andy Ng wrote:
>
> Hi Pandu,
>
> The requirement of "Custom Password Encoder with MD5,SHA-256 based on the
> third party application" doesn't seems to be available out of the box yet
> in latest CAS version,
>
> [as seem here: "
> https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties-Common.html#password-encoding
> "]
>
>
> What you can try is create your custom password encoding by following the
> paragraph under the link above. I do think it will take some time to
> implement such feature.
>
> Cheers!
> - Andy
>
>
> On Thursday, 23 August 2018 21:30:48 UTC+8, Ranga Nadha wrote:
>>
>> Hi Andy/Colin,
>>
>> Thanks for the reply, I have added the OJDB dependency in the pom.xml and
>> the exception is gone.
>>
>> Now CAS is connecting to the database for authentication purpose.
>>
>> But the problem is we have a custom password encoder, MD5,SHA-256 based
>> on the third party application rule the encoding format will decide.
>>
>> So, our requirement is to call the third party application
>> passwordEncoding class for the encodingAlgorithm.
>>
>> Could you please tell me how to set the third-party class in the
>> application.properties for passwordEncryption.
>>
>> Thanks,
>> Pandu Ranga T.
>>
>> On Tuesday, 21 August 2018 21:19:46 UTC+5:30, Ranga Nadha wrote:
>>>
>>> Hi Everyone,
>>>
>>> We are using CAS 5.1.8 and I am trying to connect to the database for
>>> authentication purpose.
>>>
>>> I have followed the below procedure but I am getting exceptions.
>>>
>>>
>>>- Downloaded the CAS 5.1.8
>>>- Modify POM.xml with the following dependency
>>>
>>>
>>> org.apereo.cas
>>> cas-server-support-jdbc
>>> ${cas.version}
>>>
>>>
>>> log4j-slf4j-impl
>>>
>>>
>>> org.codehaus.groovy
>>> groovy-jsr223
>>>
>>>
>>>
>>>
>>> org.apereo.cas
>>> cas-server-support-jdbc-drivers
>>> ${cas.version}
>>>
>>>
>>> org.apereo.cas
>>> cas-server-support-jdbc-authentication
>>> ${cas.version}
>>>
>>>
>>>- Build cas project using mvn clean install.
>>>- Take the war file and deploy in tomcat.
>>>- In the extracted cas war.
>>>- Go to Tomcat/webapps/cas/WEB-INF/classes/appliation.properties and
>>>add the below properties.
>>>
>>> cas.authn.jdbc.query[0].sql=SELECT * FROM USERS WHERE USER_ID=?
>>> cas.authn.jdbc.query[0].url=jdbc:oracle:thin:@xxx..local:1521:db12c
>>> cas.authn.jdbc.query[0].dialect=org.hibernate.dialect.Oracle12cDialect
>>> cas.authn.jdbc.query[0].user=
>>> cas.authn.jdbc.query[0].password=
>>> cas.authn.jdbc.query[0].driverClass=oracle.jdbc.OracleDriver
>>> cas.authn.jdbc.query[0].fieldPassword=PASSWORD
>>> cas.authn.jdbc.query[0].passwordEncoder.type=DEFAULT
>>> cas.authn.jdbc.query[0].passwordEncoder.characterEncoding=UTF-8
>>> cas.authn.jdbc.query[0].passwordEncoder.encodingAlgorithm=SHA1
>>> cas.authn.jdbc.query[0].passwordEncoder.secret=
>>> cas.authn.jdbc.query[0].passwordEncoder.strength=16
>>>
>>>
>>> cas.authn.accept.users=
>>> logging.level.org.apereo=DEBUG
>>>
>>> *I am getting the below error*
>>>
>>> 2018-08-21 21:00:02,828 DEBUG
>>> [org.apereo.cas.adaptors.jdbc.config.CasJdbcAuthenticationConfiguration] -
>>> >> me, sn=sn, cn=commonName}] for
>>> [jdbc:oracle:thin:@..local:1521:dev12c]...>
>>> 2018-08-21 21:00:02,870 ERROR [com.zaxxer.hikari.HikariConfig] - >> to load class of driverClassName oracle.jdbc.OracleDriver in HikariConfig
>>> class classloader
>>> ParallelWebappClassLoader
>>> context: cas
>>> delegate: false
>>> --> Parent Classloader:
>>> java.net.URLClassLoader@13221655
>>> >
>>> 2018-08-21 21:00:02,870 ERROR
>>> [org.apereo.cas.configuration.support.Beans] - >> [Failed to load class of driverClassName [oracle.jdbc.Oracle
>>> Driver] in either of HikariConfig class loader or Thread context
>>> classloader]>
>>>
>>> Can any one help to resolve this issue.
>>>
>>> Thanks in advance,
>>>
>>> Thanks,
>>> Pandu Ranga T.
>>>
>>
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/f9504605-44c2-4d7a-a440-f78eaae1d011%40apereo.org.
Re: [cas-user] remember me use
Vallee, When you say session, are you talking about the CAS session or the client session? Is it possible to have a cookie that expires when the browser closes and lives for a set time? You can use this to have the cookie expire when the browser closes: cas.tgc.maxAge=-1 I have this note in my config (not sure if it applies to 5.2) but our config is set to expire TGC when browser closes: # default is P14D # used to set maxAge on user selection of remember me at login # it is always set regardless of user choice; this is a bug to investigate # file: https://github.com/apereo/cas/blob/5.1.x/support/cas-server-support-cookie/src/main/java/org/apereo/cas/web/support/CookieRetrievingCookieGenerator.java cas.tgc.rememberMeMaxAge=-1 I do not have these in my config: cas.ticket.tgt.timeToKillInSeconds cas.ticket.tgt.maxTimeToLiveInSeconds Ray On Mon, 2018-08-27 at 02:51 -0700, vallee.romain wrote: Hello, We have migrate from 4.2 to 5.2. Our need is simple, but we can't implement it . We put the option "remember me", with a delay of 6 months ( about). But even following the documentation, it is impossible to have a session maintained for more than a few hours by checking the "remember me" box. i try so many configuration... my last configuration is : cas.tgc.rememberMeMaxAge=1209600 cas.ticket.tgt.timeToKillInSeconds=172800 cas.ticket.tgt.maxTimeToLiveInSeconds=135 cas.ticket.tgt.timeout.maxTimeToLiveInSeconds=135 cas.ticket.tgt.rememberMe.enabled=true cas.ticket.tgt.rememberMe.timeToKillInSeconds=135 did anyone manage to make it happen: when you check "remember me" to have a session maintained for XX months when you do not check "remember me" with the session that closes at the end of the browser with a maximum time of XX hours. I'd be very interested! Best regards -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | r...@uvic.ca -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1535388778.2864.10.camel%40uvic.ca.
[cas-user] CAS 5.3.x Introduces Breaking Change for RequestID in cas-server-support-saml
CAS 5.3.x introduces a breaking change to how RequestIDs are handled when
validating SAML Services.
*In 5.2.x (and all previous version of CAS), if the RequestID is not
present, it will gracefully fail by returning a null value:*
https://github.com/apereo/cas/blob/5.2.x/support/cas-server-support-saml/src/main/java/org/apereo/cas/support/saml/authentication/principal/SamlServiceFactory.java
requestId = extractRequestId(requestBody);
/**
* Extract request id from the body.
*
* @param requestBody the request body
* @return the string
*/
private static String extractRequestId(final String requestBody) {
if (!requestBody.contains("RequestID")) {
LOGGER.debug("Request body does not contain a request id");
return null;
}
try {
final int position = requestBody.indexOf("RequestID=\"") +
CONST_REQUEST_ID_LENGTH;
final int nextPosition = requestBody.indexOf('"', position);
return requestBody.substring(position, nextPosition);
} catch (final Exception e) {
LOGGER.debug("Exception parsing RequestID from request.", e);
return null;
}
}
*In 5.3.x, if the RequestID is not present it will throw a
NullPointerException:*
https://github.com/apereo/cas/blob/5.3.x/support/cas-server-support-saml/src/main/java/org/apereo/cas/support/saml/authentication/principal/SamlServiceFactory.java#L63
*@NonNullfinal Attribute requestIdAttribute =
requestChild.getAttribute("RequestID"); requestId =
requestIdAttribute.getValue();This change will break all versions of
apereo/mod_auth_cas (See:
https://github.com/apereo/mod_auth_cas/issues/148) along with any other
client that does not properly implement support for the RequestID
parameter.*
This change should be reverted (this is as simple as removing the @NonNull
Lombok annotation so the request will failback to a null response).
Breaking every install of mod_auth_cas along with other legacy clients
cannot be considered acceptable.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/bb707ba1-3a60-4cb8-beff-17997dccb514%40apereo.org.
