Skyhook Self Service Portal

Using Skyhook Self Service Portal

Skyhook Self Service Portal

The skyhook self service portal can be used to create new skyhook tenants and renew expiring dbAccessTokens for extensions that use our skyhook service. Customers can access the portal on this link https://clearpass.arubanetworks.com/webhooks/skyhook and can login using their HPE passport credentials.

This portal allows administrators to create skyhook tenants for various integrations that support webhook notifications. Upon registering for a skyhook tenant you are provided with a ‘Tenant ID’ that can be used in the “skyhookTenant” field and a DB token that goes in the “dbAccessToken” field of the extension configuration. Once a tenant is registered, the dbAccessToken for the tenant is valid for a year. For an uninterrupted service, customers are required to renew their DB token by logging in to the portal and following the renewal steps. All registered skyhook tenants are mapped under the HPE Passport used to login to the self service portal.

The portal gives a list of all registered tenants including the App name (Integration e.g Jamf, Envoy etc), the expiration date and time until expiration to let administrators choose when they want to renew the DB token as per their convenience.

Using the Skyhook Self Service Portal

Creating a new Skyhook Tenant

  • Go to https://clearpass.arubanetworks.com/webhooks/skyhook and click on ‘Login with HPE SSO’ option.



  • Enter your HPE passport credentials to login.

INFO

The HPE passport credentials used to login to the skyhook self service portal should be associated with a tenant that has a valid support license on their HPE Aruba Networking ClearPass Policy Manager. If there are no ClearPass Policy Manager appliances with valid support licenses registered under the HPE passport credentials used to login then the below error is displayed despite the credentials are valid





  • The landing page displays the skyhook tenants registered with the HPE Passport credentials under the ‘Your Tenants’ page.

INFO

Note that the old tenants created using the legacy manual method will not show up in the self service portal. As an initial onboarding step, a new tenant has to be created. This creates a new new tenant ID and DB Access Token. The tenant ID needs to be updated both within the extension configuration and also in the 3rd party application sending notifications to skyhook. The DB Access Token needs to be updated within the extension configuration.





  • To create a new tenant Click on ‘Register Tenant’.



INFO

Note that the portal reaches out to the domain “skyhook.clearpassbeta.com” for creating new tenant. The domain and the URL should be allow listed through any endpoint security or SSE solutions installed on the device you are accessing the portal from and also through firewalls that the traffic is traversing through.

https://skyhook.clearpassbeta.com/api/register/<name-of-extension>

If the portal is unable to reach the tenant registration URL, you might see an error as shown below.



  • Choose the integration name as needed from the ‘App’ dropdown, Enter a suitable label and click on ‘Register’.



  • The tenant and the DB token is displayed. Ensure to copy / download the details as the token is displayed only once. Once done, click ‘OK’ to return to the ‘Your Tenants’ page.



  • Once you have the SkyhookTenant and the dbAccessToken, You can continue with the further ClearPass Extension configuration as per the steps decribed in the integration guide for the extension you are installing. Existing integrations which were using legacy manually provisioned tenant ID, would have to ensure that the tenant ID is updated on the third-party application with the new one from self-service portal.

INFO

When configuring Webhook HTTP Servers in the third-party application, please use the following Target URL:

https://skyhook.arubasecurity.net/api/skyhook/{{extension-id}}/{{skyhook-tenant-id}}

Where:

{{extension-id}} can be any of the following depending upon which application you are sending webhooks from

jamf / envoy / sine / processor (for Generic Skyhook Processor) / meraki / teem / airwatch (for VMware Workspace ONE)

{{skyhook-tenant-id}} would be the new tenant ID created from the self-service portal

Example: https://skyhook.arubasecurity.net/api/skyhook/jamf/ab45xxxx-bcd4-cd45-ef34-abcde11xxxxx

TIP

For Envoy integration, ensure that the tenant ID is updated separately for each location to ensure each location is using the new tenant ID to send the notifications

Renewing the DB token

  • Select the Tenant that needs DB token renewal. You can use the Search box to search for Tenants based on their Tenant name or Label on the upper left corner of the page.



  • Click on the ‘Renew’ option under the ‘Actions’ column to proceed with the renewal of the DB token.



  • The tenant and the DB token is displayed. Ensure to copy / download the details as the token is displayed only once. Once done click ‘OK’ to return to the ‘Your Tenants’ page.



INFO

Once the dbAccessToken is renewed, Ensure that you update the dbAccessToken field in the extension configuration immediately to avoid longer service outages as renewing the dbAccessToken disables the existing token.


Last modified: November 11, 2025 (d5afdd32)