Service Robot Configurations

┌─────────────────────────────────────────────────────────────────────────────┐
│               Service Robots on node1 (Version X.X.X build XXXX)            │
└─────────────────────────────────────────────────────────────────────────────┘

┌─┬───────────────────────────────────────────────────────────────────────────┐
│1│Certificate Check Robot                                                    │
└─┴───────────────────────────────────────────────────────────────────────────┘

Move the cursor or enter a it's corresponding number (Q to Quit)

Main> System Settings> Service> REST API> Service Robots>

Certificate Check Robot

Certificate Check Service Robot

Service Robots are used to trigger actions within the StoredSafe appliance. The
Certificate Check Service Robot is accessed thru the URI:

    https://node1/api/1.0/certificatecheck/<days>

Accessing this URI will return a JSON array with all X.509 certificates about to
expire within specified number of days.

Certificate Check Service Robot access is currently only permitted from:

127.0.0.1 [Internal required Service Robot access]

Note

This endpoint is unauthenticated — access control is purely IP-based via this allow-list. 127.0.0.1 is required internally and should not be removed. Only add networks here that you specifically want to be able to query certificate expiry data without any credentials.

Allow Certificate Check Service Robot access from up to 100 networks. (Use IPv4 or IPv6 with CIDR notation, 192.168.0.0/24 or 2001:db8:cafe::/48)

Press return to keep the suggested <DEFAULT> values. To end input at any time, simply enter a single dot (.) and press return.

Network #0 (. to end input, Q to Quit) <127.0.0.1>: