Skip to main content

Space Pinger

Last updated: Mon, 09 Oct 2017 21:51:12 GMT
iOFFICE Knowledge Center

Space Pinger

Summary

This section describes how to configure the Space Pinger. Implementation is very similar to the single sign on integration. The Space Pinger is commonly used to integrate into directory systems (e.g. Lotus Notes, Exchange) or lobby kiosks to view a live floor plan of an employee’s location. 

 

Note: The Space Pinger now uses HTML 5 instead of Flash. This means decreased loading times, and you can now access this function using your mobile device. 

 

Hash Based

The hash based interface is a simple method of passing the needed information to the Pinger.

Details

The customer’s corporate intranet provides a unique key for the desired user, generates a hash and forwards the user to a URL. The hash is used to verify the link was generated by an authorized source, such as the customer’s corporate directory.

 

The hash is generated in part the target user’s identifying value concatenated by a pipe (|) and a salt. The directory pinger salt is a string, similar to a password, provided to iOFFICE by the customer. Optionally, adding the current date (in GMT/UTC) ensures that the hash is only valid for twenty-four hours. Append the date to the hash using the YYYY-MM-DD format.

URL

The below address is the URL the customer’s intranet will forward the user to. Parameters are accepted via HTTP GET.

 

https://customer.example.com/external/api/space/pinger/Sample Hash Results

Sample Hash Results

The customer’s developer verifies their hash implementation using the below samples. 

Note: MD5 is shown here for illustrative purposes only. While MD5 is technically available, SHA-256 will be implemented on all future integrations.

Pseudo Code Hash Result

SHA-256 ("targetemployeeid|mysalt")

c2fa6b06f6a0c3822958b1cb44c58f62ae02bde2f8ae351bb1226f88189e3581

SHA-256 ("targetemployeeid|mysalt|2017-10-07")

2e9a09866bbaaf51cd58f76319ee1fed9909de6589a8d25fc6988d16a12c12f4

MD5 ("targetemployeeid|mysalt")

817650159B3DE27CFB6AF571ADB5C285

MD5 ("targetemployeeid|mysalt|2008-05-07")

593C5BD83F8D7C476399B383605D03F4

Parameters

Name Value

method

(required) 

The value should always be hash when using this method 

property

(required) 

Ex: ‘employeeid’, ‘email’, ‘username’, 'floorid', 'roomid' 

target

(required) 

The value used to identify the user (see property).

Note: To find Room IDs or Floor IDs, you can use the Insights module or the REST API.

hash

(required) 

A SHA-256 representation of the id (target), a salt, and optionally a date; these fields are to be separated by the pipe character. 

Example Call

As an example, a users browser would be directed to the below by the customer’s intranet or back end systems:

 

https://siteurl/external/api/<wbr/>space/pinger/?method=hash&<wbr/>target=000000&property=<wbr/>employeeid&hash= 4E05717C11BAAAC91A95955BC8AEAD<wbr/>D1 

 

 

 

 

Related Topics

Integration

Automated User Provisioning

Common Logon, Single Sign On, or Federated Identity

Local File Repository

  • Was this article helpful?