Your Identity Cloud service instance is identified by its custom_name.

The custom name must be unique and may contain only lower case letters (a-z) or digits (0-9). Underscore (_) or hyphen (-) cannot be used.

IP address

Ubisecure will assign a public IP address for your Identity Cloud service instance:

• Your service endpoint public IP address (provided by Ubisecure)

Domain name

You can either choose the default (custom_name.onubisecure.com) domain or use your own domain name managed by the customer:

• Ubisecure managed DNS (default)
• Customer managed DNS and mail server

Ubisecure managed DNS

If your Identity Cloud service instance has the default Ubisecure managed DNS, it will be reachable at the following addresses:

Ubisecure provides the mail services (SMTP) for Ubisecure managed DNS. No action is required on the customer's part.

Customer managed DNS

With customer managed DNS, all the above URI addresses will have a different host name as given by the customer.

If your Identity Cloud service instance has customer managed DNS, the customer is responsible for managing the following public DNS Resource Records (RRs):

Customer may choose all the above host names freely under the customer's domain. Use of the custom_name is optional in customer given host names. Any valid host names ( RFC-1123) under the customer's domain can be used.

Customer mail server

With customer managed DNS, the customer is responsible for providing an SMTP server for the Identity Cloud service instance:

• SMTP host name
• Port (usually 465 or 587)
• Security protocol (STARTTLS, TLS, SSL)
• User name
• Password
• From-address (default: noreply@example.com)

The customer is responsible for their domain email security configuration and related DNS records such as SPF, DKIM, DMARC, and similar.

Customer managed network security

The Identity Cloud service has robust security policies and procedures in place. The service does not require additional customer managed security measures unless the customer has specific requirements of their own.

The customer is responsible for opening access to the above service endpoints from the authorized source networks.

The customer is responsible for enabling access to their provided SMTP service from the following addresses:

If special arrangements have been agreed for custom applications, customer is responsible for any relevant configurations at their end.

VPN is available as an additional option on request.

Retrieving service instance logs

You can retrieve your Identity Cloud service instance logs via SFTP.

Customer SSH key pairs

The customer is responsible for managing one or more SSH key pairs for access to the Identity Cloud service instance logs. Send your SSH public keys to Ubisecure for access to the logs:

• Your SSH public key(s)

Keep your private keys secret. Do not send the private keys to Ubisecure or anyone else.

SFTP connection via SSH proxy

1. Add your private key to an SSH authentication agent before connecting. The proxy command uses SSH agent forwarding to authenticate your connection to the log server.

ssh-add

2. The log server will be reachable via SFTP using the following proxy command:

sftp -o "ProxyCommand ssh -W %h:%p %r@manage.custom_name.example.com" monitor@logs


# or the old usage
# sftp -o "ProxyCommand ssh -A %r@manage.custom_name.example.com nc %h %p" monitor@logs

Use the SFTP commands to browse the logs on the server.

On Windows using WinSCP and PuTTY

Configure WinSCP to use the Plink and Pageant programs that come with PuTTY.

• Download Putty
• Download WinScp

1. Add your private key to Pageant (SSH authentication agent) before connecting.

2. Connect to log server via Putty: 

3. The log server will be reachable using the following WinSCP configuration:

Session / File protocol: SFTP

Host name: logs

User name: monitor

Advanced...

Connection → Keepalives / Sending of null SSH packets

Seconds between keepalives: 120

Connection / Proxy → Proxy type: Local

Proxy host name: manage.custom_name.example.com

User name: monitor

Proxy settings / Local proxy command: ^{"C:\\Program Files (x86)\\PuTTY\\plink.exe" %user@%proxyhost -nc %host:%port}