JIRA logs all issues back to 3.0.0. You may need to expand the view to see it all or switch to the Road Map or Change Log View.
If all you've done is extend code and modify Spring configuration it shouldn't be a difficult upgrade (though we've continually refined the Spring configuration stuff). The Jasig CAS Client for Java supports the Single Log Out. -Scott On Wed, Apr 1, 2009 at 11:38 AM, Sukma Agung Verdianto <[email protected]>wrote: > Hi Scoot, > Thanks for the reply. > Anyway, I see that JIRA is only log issues started from version 3.3 which > is quite far from what we use now. > > Does 3.0.5 and 3.3 have different architecture? > If not, then the upgrade process shouldn't very difficult, probably. We did > not modify core code but instead extending some classes and change some > spring configuration. > > If we then decide to use CAS 3.3 and its logout mechanism, is there any > Java CAS client that already support single sign out? > Or we should implement that manually (ticket-session id mapping, request > parsing, etc) ? > > Regards, > Sukma > > On Wed, Apr 1, 2009 at 9:13 PM, Scott Battaglia <[email protected] > > wrote: > >> A compete list of changes between all CAS Servers can be found in the JIRA >> instance: >> http://www.ja-sig.org/issues/browse/CAS >> >> >> On Wed, Apr 1, 2009 at 6:08 AM, Sukma Agung Verdianto >> <[email protected]>wrote: >> >>> Hi All, >>> Could somebody provide me a list of CAS changes from version 3.0.5 to >>> current stable version of CAS? features and architecture. (links to a >>> website is OK) >>> >>> The reason why I'm asking this is our system is currently using CAS 3.0.5 >>> (up more than 2 years) and we are considering an upgrade to the latest >>> version of CAS. >>> We have extend CAS, implement our custom Single Sign Out solution (which >>> I believe this has not been supported out of the box at that time), theming >>> support, and add extra behavior to authentication process. >>> And since we have spent some effort of developing our custom code, we did >>> not focused to do a routine upgrade for our CAS system. >>> >>> We are really interested to upgrade the CAS and to use >>> its built-in features (Single Sign Out, SAML protocol, etc) instead of using >>> our custom code. >>> We need to estimate how big the effort to upgrade before we decide it. >>> Any suggestion are welcome. >>> >>> Regards, >>> Sukma >>> >>> -- >>> You are currently subscribed to [email protected] as: >>> [email protected] >>> >>> >>> >>> >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/cas-user >>> >>> >> -- >> You are currently subscribed to [email protected] as: >> [email protected] >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> >> > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
