SSO Tru64

From: Todd Wesley (todd_at_lakotaonline.com)
Date: 03/18/05

  • Next message: Subhash P: "Tar Restore problem" 
    Date: Fri, 18 Mar 2005 13:58:45 -0500
To: "tru64-unix-managers@ornl.gov" <tru64-unix-managers@ornl.gov>, "UreyD@pginw.com" <UreyD@pginw.com>

    I saw your post below...we are interested in doing the same thing...did
    you find out any negative implication changing to Basic Security on
    Tru64 and using SSO would have?

    Thanks!

     Todd C. Wesley
    Network and Systems Manager
    Lakota Technology Department

    *****************PRIVATE AND CONFIDENTIAL *********************** This
    electronic message transmission contains information from the Lakota
    Local School District that is privileged, confidential or otherwise the
    exclusive property of the intended recipient or the Lakota Local School
    District. This information is intended for the use of the individual or
    entity that is the intended recipient. If you are not the designated
    recipient, please be aware that any dissemination, distribution or
    copying of this communication is strictly prohibited. If you have
    received this electronic transmission in error, please notify us by
    telephone (513) 644-1200, collect, or by electronic mail
    email@lakotaonline.com and promptly destroy the original transmission.

    We are currently running enhanced security but are contemplating using
    SSO.
    According to the documentation, enhanced security cannot be enabled to
    run
    Windows SSO. Can I changed the system back to BASE security? Will this
    have any adverse effect besides losing the enhanced capabilities?

    Thanks,

    Dawn Urey
    PGI
    Systems and Site Support Manager
    (919)874-9512

    ------------ PGI Internet E-mail Confidentiality ------------ Please
    note:
    This message may contain information which is privileged and
    confidential.
    If you are not the intended recipient, you are hereby notified that any
    dissemination, distribution or copying of this communication is strictly
    prohibited. If you believe you have received this message in error,
    please
    forward to Postmaster@pginw.com.

  • Next message: Subhash P: "Tar Restore problem"

    Relevant Pages

    • RE: RE: Value of certifications
      ... entities other than the intended recipient is prohibited. ... Security' that may be interesting. ... My employer will not pay for certifications, ... you're in is a very good place from which to build your skills. ...
      (Security-Basics)
    • Re: Manifest Files & VS2005
      ... I'm fairly new to .NET app security and manifests. ... confused - if the manifest file is embedded into the assembly, ... If I choose "This is a partial trust application" and then include some ... Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. ...
      (microsoft.public.dotnet.languages.csharp)
    • Manifest Files & VS2005
      ... I'm fairly new to .NET app security and manifests. ... confused - if the manifest file is embedded into the assembly, ... If I choose "This is a partial trust application" and then include some ... intended recipient, please inform the sender and delete all copies. ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: WindowsTokenRoleProvider & Domain Groups
      ... Also, regarding the DLGs, it occurs to me to ask whether or not the groups ... your access token unless the groups are security enabled and the domain in ... ADFS = Active Directory Federated Services? ... SSO = Single Sign-On? ...
      (microsoft.public.dotnet.framework.aspnet.security)
    • Re: Cold Fusion SSO and File Access
      ... SSO is private to the CF application, ... > I am a security engineer who just completed an Cold ... The web server is obviously IIS. ... > authenticate to the windows server. ...
      (microsoft.public.inetserver.iis.security)