Tagged with spnego - Visokio Forums http://forums.visokio.com/discussions/tagged/spnego/feed.rss Mon, 30 Oct 17 15:04:06 -0400 Tagged with spnego - Visokio Forums en-CA Security: SPNEGO Troubleshooting http://forums.visokio.com/discussion/2571/security-spnego-troubleshooting Tue, 27 May 2014 05:05:11 -0400 Veaceslav 2571@/discussions Mobile Web Server Authentication

SPNEGO Troubleshooting


  • Error Java Cryptography Extension (JCE) Unlimited Strength is not enabled.
    LDAP/Active Directory (AD) server may send tickets that have been encrypted using AES 256 bits (or larger) which is not enabled in Java (JRE) by default and therefore SPNEGO authentication may fail

    Java Cryptography Extension (JCE) Unlimited Strength includes two jar files that contain only configuration settings enabling unlimited strength cryptography algorithms in Java.

    To enable JCE unlimited strength download it from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

    The downloaded file contains three files

    • local_policy.jar
    • US_export_policy.jar
    • README.txt

    Read and follow the instructions outlined in the README.txt file.

    To install JCE unlimited strength, the client needs to put these two jars in
    - {OMNISCOPE LOCATION}\x86\lib\security
    - {OMNISCOPE LOCATION}\x64\lib\security
    while creating a backup for the existing (default) two files and restart the application

]]> Security: Single-Sign-On (SPNEGO) Configuration http://forums.visokio.com/discussion/2566/security-single-sign-on-spnego-configuration Fri, 23 May 2014 10:32:45 -0400 Veaceslav 2566@/discussions Mobile Web Server Authentication

Single-Sign-On (SPNEGO) Mechanism

SPNEGO (Single-Sign-On) mechanism allows users to authenticate automatically with their LDAP/Active Directory (AD) account without asking them for credentials. Having a proper setup, authorized users never type their credentials in any dialog or form. Unauthorized users, however, are either prompted for credentials or are denied server access.
  • Users are stored and managed by an LDAP/AD server
  • Omniscope Mobile server is configured to ask the LDAP/AD server to validate user tokens

Configuration

At least three machines are involved in a Single-Sign-On setup:

  1. LDAP/AD server (e.g. computer name ldapserver)
  2. A machine running Omniscope server (e.g. computer name omniscopeserver)
  3. A client machine having a browser installed (Chrome, Firefox, Internet Explorer, etc) (e.g. computer name browserA)

Note: Single-sign-on does not work when the client (browser) runs on the same machine as Omniscope server (or LDAP/AD)

  • The machines must be on the same intranet network,
  • on the same domain (e.g. example.com),
  • DNS properly setup such that they all can nslookup each other by name (e.g. nslookup omniscopeserver finds the machine running omniscope server)

  1. LDAP/AD machine - Windows Server OS (2003, 2008, 2012, etc)
    • Create a dedicated LDAP user on the domain, e.g. omniscopeuser@example.com with password YourPassword (choose a stronger password), make sure the password never expires
    • In command prompt execute:
      setspn -A HTTP/omniscopeserver.example.com omniscopeuser


      image
      where example.com is your network domain
      omniscopeserver is the name of the machine running Omniscope server
      omniscopeuser is user logon name of the dedicated LDAP user
      HTTP/omniscopeserver.example.com has never been mapped before with other user. If it has, you need to remove it first:
      setspn -D HTTP/omniscopeserver.example.com otheruser

    • In command prompt, execute the second command (make sure to use capital letters exactly as shown in the command):
      ktpass -princ HTTP/omniscopeserver.example.com@EXAMPLE.COM -pass YourPassword -mapuser omniscopeuser@EXAMPLE.COM -out omniscopeuser.HTTP.keytab -crypto RC4-HMAC-NT -kvno 0
      • where example.com is your network domain
      • HTTP/omniscopeserver.example.com - Kerberos service principal name for SPNEGO
      • omniscopeuser - the dedicated SPNEGO user that has been created on the LDAP server
      • YourPassword - password of the dedicated SPNEGO user
      • RC4-HMAC-NT - cryptosystem to use when sending SPNEGO tickets
      • kvno - Key version number

      image

    Obviously, LDAP/AD needs to have regular users defined, users that are about to use Omniscope at least. For the purpose of this tutorial we will consider that
    there is a user clientA@example.com with password ClientPassword

  2. Omniscope server machine

    • Start Omniscope server

      image

    • On Mobile Web Server service section click Config, scroll down to Default folder configuration and click Edit

      image

    • Edit SPNEGO global settings, for principal name type:
      HTTP/omniscopeserver.example.com
      and edit the password for that LDAP account ('YourPassword')

      image

      image

    • Click OK to close editing SPNEGO global settings
    • Either create a new group with new permissions, or edit an existing group

      image

    • Add a new authentication mechanism and choose SPNEGO mechanism

      image

    • Make sure you add all user names for the users that will be allowed to authenticate automatically (e.g. clientA, no domain needs to be included in the name)

      image

      image

    • Click OK to close each dialog and click Save and apply to save the configuration
    • Omniscope server does not need to be restarted manually

  3. Client Machine - The browser has to be configured to use Single-Sign-On and trust omniscopeserver machine

    • For Internet Explorer

      • Open Internet Options

        image
      • In Security tab select Local intranet and click Sites button - make sure all check boxes are selected:
        Automatically detect intranet network,

        image
        • Include all local intranet sites not listed in other zones,
        • Include all sites that bypass the proxy server,
        • Include all network paths


        Then click Advanced button and add the name of the omniscopeserver or the full name (with domain) as it is going to be used to access the omniscope server from the browser
        Note: The browser cannot use Single-Sign-On when accessing the omniscopeserver by IP instead of name, and the name has to be added to the zone

        image

      • Click Close then OK to close the Local intranet dialogs
      • Click Custom Level... button, scroll down to User Authentication and select Automatic logon with current user name and password then click OK to close the dialog

        image

      • In the Advanced tab of the Internet Options dialog scroll down to Security section and make sure Enable Integrated Windows Authentication option is selected. (It should be selected by default)

        image

      • Click OK to close Internet Options dialog
      • Restart Internet Explorer
      • Test it: open http://omniscopeserver you should be able to use omniscope server if you have the right permissions (group permissions that you set up on Omniscope server)

    • Google Chrome
      • Google’s Chrome browser shares the same configuration with Internet Explorer. Once the trusted URL is added in Internet Explorer, Chrome works with SPNEGO. Chrome does not have a configuration mechanism.

    • Mozilla Firefox
      • In the address bar type:
        about:config

        image

        and search for trusted. The required key is a comma separated parameter named network.negotiate-auth.trusted-uris - edit it to include 'omniscopeserver' as well
        image


]]>