Results 1 to 2 of 2

Thread: Do Authentication objects need to be immutable?

Hybrid View

  1. Feb 10th, 2005, 05:36 PM #1
    moritz
    moritz is offline Junior Member
    Join Date
    Feb 2005
    Posts
    4

    Default Do Authentication objects need to be immutable?

    Do Authentication objects need to be immutable?

    RunAsUserToken claims that it is. What about the others?

    What are the consequences, if they weren't?

    Thanks.

    Andreas
  2. Feb 11th, 2005, 12:33 AM #2
    Ben Alex
    Ben Alex is offline Senior Member Spring Team
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    2,768

    Default

    No, they don't need to be immutable. Using immutable objects simply protects an object from inadvertant modification.
« Previous Thread | Next Thread »

Similar Threads

  1. Putting Objects in the Session when Authentication Successfu
    By linus1412 in forum Security
    Replies: 7
    Last Post: Nov 2nd, 2005, 04:47 AM
  2. Problem: SecureContextImpl reused in subsequent session
    By jgraves in forum Security
    Replies: 2
    Last Post: Oct 13th, 2005, 02:47 PM
  3. Loosing my SecureContext
    By sklakken in forum Security
    Replies: 3
    Last Post: Jul 21st, 2005, 01:44 PM
  4. Method call why not be intercepted by MethodSecurityIntercep
    By aaron8tang in forum Security
    Replies: 8
    Last Post: Dec 7th, 2004, 06:13 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules