Re: [cas-user] [CAS] Automatically updated Time-based access strategy extension to current date
Interesting, I will look into that. Thanks for your reply. Il giorno giovedì 21 gennaio 2021 alle 17:05:41 UTC+1 Misagh Moayyed ha scritto: > Probably not "less custom", but I would either write my own access > strategy or use the one based on aan external groovy script to embed > logic in there. > > On Thu, Jan 21, 2021 at 7:54 PM Davide Malacrida > wrote: > > > > Hello everyone, > > > > Lately we have been working on a locally deployed instance of Apereo > CAS, in order to study the product a bit. We have the following doubt > regarding how time-based service access strategy should be configured. > > > > > > > > In order to implement this functionality, we have used the time-based > access strategy extension, as described in the documentation ( > https://apereo.github.io/cas/5.2.x/installation/Configuring-Service-Access-Strategy.html#time-based). > > However, the documentation only described how one can set a static date and > time for this policy. Instead, we wanted the attributes startingDateTime > and endingDateTime to be automatically updated with the current date. In > order to do this, we have created a custom script. This script is scheduled > to run every day at the same hour and basically writes the values of these > attributes, so that they are always updated with the current date. > > > > > > > > We were wondering, is this the way time-based access strategy is > supposed to be implemented? Is there another less custom way that should be > used in order to achieve this result? > > > > > > > > Thanks for your help, > > > > Davide Malacrida > > > > IAM Functional Analyst > > > > -- > > - 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+u...@apereo.org. > > To view this discussion on the web visit > https://groups.google.com/a/apereo.org/d/msgid/cas-user/1920ce52-3ea4-4bc5-8b59-973186abf819n%40apereo.org > . > -- - 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/baf46e82-70bf-4677-8e54-37fdbed0e476n%40apereo.org.
Re: [cas-user] [CAS] Automatically updated Time-based access strategy extension to current date
Probably not "less custom", but I would either write my own access strategy or use the one based on aan external groovy script to embed logic in there. On Thu, Jan 21, 2021 at 7:54 PM Davide Malacrida wrote: > > Hello everyone, > > Lately we have been working on a locally deployed instance of Apereo CAS, in > order to study the product a bit. We have the following doubt regarding how > time-based service access strategy should be configured. > > > > In order to implement this functionality, we have used the time-based access > strategy extension, as described in the documentation > (https://apereo.github.io/cas/5.2.x/installation/Configuring-Service-Access-Strategy.html#time-based). > However, the documentation only described how one can set a static date and > time for this policy. Instead, we wanted the attributes startingDateTime and > endingDateTime to be automatically updated with the current date. In order to > do this, we have created a custom script. This script is scheduled to run > every day at the same hour and basically writes the values of these > attributes, so that they are always updated with the current date. > > > > We were wondering, is this the way time-based access strategy is supposed to > be implemented? Is there another less custom way that should be used in order > to achieve this result? > > > > Thanks for your help, > > Davide Malacrida > > IAM Functional Analyst > > -- > - 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/1920ce52-3ea4-4bc5-8b59-973186abf819n%40apereo.org. -- - 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/CAGSBKkdHXjrGT4eMZuQgy%3DRr6kLSY1nYcuUEH3fDDjz5RogWWA%40mail.gmail.com.
[cas-user] [CAS] Automatically updated Time-based access strategy extension to current date
Hello everyone, Lately we have been working on a locally deployed instance of Apereo CAS, in order to study the product a bit. We have the following doubt regarding how time-based service access strategy should be configured. In order to implement this functionality, we have used the time-based access strategy extension, as described in the documentation ( https://apereo.github.io/cas/5.2.x/installation/Configuring-Service-Access-Strategy.html#time-based). However, the documentation only described how one can set a static date and time for this policy. Instead, we wanted the attributes *startingDateTime* and *endingDateTime* to be automatically updated with the current date. In order to do this, we have created a custom script. This script is scheduled to run every day at the same hour and basically writes the values of these attributes, so that they are always updated with the current date. We were wondering, is this the way time-based access strategy is supposed to be implemented? Is there another less custom way that should be used in order to achieve this result? Thanks for your help, *Davide Malacrida* IAM Functional Analyst -- - 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/1920ce52-3ea4-4bc5-8b59-973186abf819n%40apereo.org.
