Versions Compared

Old Version 5

changes.mady.by.user Rod Widdowson

Saved on

compared with

New Version 6

changes.mady.by.user Scott Cantor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning
titleNeeds review

This topic Work In Progress and requires review by a suitable macOS user

macOS Installation

The recommended strategy for macOS is now The supported Mac installation mechanism is the MacPorts system. MacPorts is a software package similar to the BSD ports facility that uses descriptors called Portfiles to download and install open source packages, either from pre-built cached binaries or from source.

Shibboleth and its dependencies have a set of official Portfiles that enable a fairly simple installation or upgrade of the entire stack on OS X 10.4+. Other versions may also work (and we can make adjustments to the Portfiles if needed).MacOS.

Of course, building Shibboleth from source is also possible.

Install using MacPorts
Build from Source

Initial Testing

You can test to ensure that the SP is running properly and the surrounding environment is correct by accessing https://localhost/Shibboleth.sso/Status from the actual web server machine. You MUST use "localhost" as the hostname or it WILL NOT WORK by default. If this test is successful, then the software is ready for further configuration.

Tip

You can also access the Status handler from other clients or using a non-localhost name, but only if you change the acl parameter in the Status Handler configuration to permit your client address or remove it entirely to open up access to anybody. The ACL is present by default because the Status handler can return some arguably sensitive information about your configuration.

Now you can progress to the Getting Started material, or if you're in the very early stages of evaluation, try a more controlled scenario by using the TestShib IdP.  (Note that before using the TestShib IdP, you'll need to complete the first step from Getting Started, setting the entityID attribute in the ApplicationDefaults element of shibboleth2.xml.)

Once you've actually configured the SP with its own settings and metadata from at least one IdP, in order to check that the SP is "working":

Protect a directory by requiring a Shibboleth session. Usually, this is already done by default for the location "/secure".

...

Next, you typically place a script inside the protected directory that dumps the web server environment. With PHP for example you could in the easiest case just place a script there with the following:

Code Block
languagephp
<?php print_r($_SERVER) ?>

A more advanced version of such a script can be found here.

...

Include Page
InitialTesting
InitialTesting