"eGo CT Community Share" - Boundless Account Setup Form

Page 1

Library Logo

Attention School Participants: This form MUST be completed for EACH school that is joining eGo CT Community Share. 

Institution Information



Institution Address




Boundless Digital Contacts
Primary Contact:





Boundless URL
Your library will be issued a unique Boundless URL. Please provide the Prefix you would like used for your library's Boundless site.  Example: PREFIX.boundless.baker-taylor.com



eread

Page 2

Patron Authentication
Patron Authentication is the method in which Boundless will authorize patrons to check out titles. 

Integrated Library System


SIP2 - Same username and password as the ILS. Requires communication with ILS via a SIP2 server.





Shared ILS Consortium




*** If you have questions regarding how to complete the authentication technical system requirements, please contact your shared ILS technical contact or your ILS vendor representative.
Clever Single Sign On


Destiny Single Sign On

By choosing No, you will need to authenticate using the Prefix method.
Login IDs and passwords will need to previously exist or be created within Destiny for this SSO (Single Sign On) method of authentication.

Integrate with Destiny
The connection to Destiny 14  or newer requires configuration in the Destiny Admin. After completion, a school APP ID and school GUID will need to be provided to Baker & Taylor. 


Library District Manager

 

Destiny Single Sign On (SSO) with Baker & Taylor's Boundless

 

Feature Description

Destiny Discover is your one-stop shop for all your physical and digital resources. Logged-in Destiny users can now access Baker & Taylor Boundless from Destiny Discover without an additional login. Users can also access Boundless with their Destiny username and password.

 

Feature Information

You can configure Destiny Library Manager so logged-in users have access to Boundless directly from Destiny Discover search results.

 

Before you begin:

Baker & Taylor/Destiny Single Sign On (SSO) only works for the production server. If you have a test server, you must identify the production server in Destiny, if you have not done so. To verify server status, go to Setup> District Options > Server Identity. Confirm the Server Status is Production Server. For more information on identifying or changing the production server, see the Server Identity topic in Destiny Help.

 

 

To enable Library Manager with Boundless:

1. Log in as the Destiny District Administrator.

2. Select Sites > Edit(Pencil Icon on the right) > District Name.

3. To retrieve the SSO information needed for Axis 360, go to the Baker & Taylor integration section, click Run Report.

o    Destiny generates a report listing the following, this information needs to be entered into your Axis 360 setup form:

·         Whether Baker & Taylor is enabled

·         District Name

·         App ID

·         Site Name

·         Site GUID

4. Click Enable Access Axis 360 Single Sign On (SSO).

5. Read the agreement. To accept it, type your name in the Name field, and then click Sign.

6. On the Edit District page, click Save.

7. If you have existing users in Axis 360, merge them with existing Destiny patrons. Use the Axis 360 ID drop-down to select what Destiny field provides the matching Axis 360 identifier.

©




ILS Information

Some ILS vendors require a Location/Institution Code.

The server URL/IP running the ILS code and the port that should be used for connection. Please check with your ILS if you are unsure of the port.







Blocked Location Code

Good Test ID's and PINS These IDs should be valid, belonging to the allowed location, and not contain any blocks




Invalid/Blocked Test IDs and PINS.  Please provide IDs from the blocked location that should not have access.




Blocked Location Code

Good Test ID's and PINS. These IDs should be valid, belongin to the allowed location, and not contain any blocks. 




Invalid/Blocked Test IDs and PINS. Please provide IDs from the blocked location that should not have access.




Test ID's
For testing purposes, please provide several valid test IDs and PINs/Passwords (if required)




Please provide several sample IDs that should be blocked and the reason for the block (e.g.: fines, lost cards and expired cards)




Axis360 can provide an error message to your patrons. What message would you like to send?




Axis360 can provide an error message to your patrons. What message would you like to send?




Axis360 can provide an error message to your patrons. What message would you like to send?

EZproxy Authentication Set Up





Polaris API








Prefix Authentication


LDAP Information

Some ILS vendors require a Location/Institution Code.
External LDAP Server
This is the URL or external IP address of the server that is running your LDAP product, as well as the port to which Boundless should connect.

Some ILS vendors require a Location/Institution Code.

The server URL/IP running the ILS code and the port that should be used for connection. Please check with your ILS if you are unsure of the port.

LDAP Bind Authentication
The login and password required to connect to the LDAP server.


LDAP Base DN

The LDAP Base DN is the base container or domain component that we begin our search from. This should be a parent directory to each of the containers that your users are located within.

For example, if you have users contained in both OU=Staff, DC=Corp, DC=Domain, DC=Com and contained in OU=Students, DC=Corp, DC=Domain, DC=Com, Boundless will use DC=Corp, DC=Domain, DC=Com as the Base DN.


LDAP Bind Authentication

The following Boundless servers need to have access to the server/port listed above.  Note: Boundless requires TCP Firewall Access instead of UDP access. If you have more than one firewall, please update all that apply.

When using LDAP, make sure that the Boundless server addresses below are added as a trusted binding source.



Network filtering for Boundless


Access to the following Boundless test and production environments must be granted.



Please provide this information to your IT Department.

       

IP addresses:   

199.184.255.217

52.226.75.12

52.226.78.36

172.171.206.4

13.82.134.120

 

 

This is used for wildcard settings in firewalls. * means the entire domain name        regardless of prefix is allowed.

            a. *.axis360.baker-taylor.com

            b. *.axisnow.com

 

If you are not able to whitelist via wildcard, then please use the below URLs.

            a. “(customers prefix).axis360.baker-taylor.com”

            b.“www.axisnow.com”

            c.“node.axisnow.com”

Test ID's
For testing purposes, please provide Test IDs and Test Passwords for developer testing.




User Identification
Please indicate what name the sample user names represent (e.g., AMAccountName, CN (Common Name), UID, etc.).

Page 3

IP Addresses for accessing Boundless


Access to the following Boundless test and production environments must be granted.


Please provide this information to your IT Department.

       

IP addresses:   

199.184.255.217

52.226.75.12

52.226.78.36

172.171.206.4

13.82.134.120

 

 

This is used for wildcard settings in firewalls. * means the entire domain name        regardless of prefix is allowed.

            a. *.axis360.baker-taylor.com

            b. *.axisnow.com

 

If you are not able to whitelist via wildcard, then please use the below URLs.

            a. “(customers prefix).axis360.baker-taylor.com”

            b.“www.axisnow.com”

            c.“node.axisnow.com”

Contact Information