License Server — Omnitouch Licensing
The License Server is the Omnitouch licensing authority the network functions check against. Every Omnitouch product — the MME, HSS, DRA, PGW-C, UPF, SGW-C, SMSC, CSCF and the rest — validates its entitlement against the License Server before it runs, asking whether a given licensee is licensed for that product and whether the licence is still within its validity window. The server holds cryptographically signed licences, each granting a licensee a set of products with a validity period and metadata, and it answers entitlement queries and records every request it is asked. Because a licence is only meaningful against a trustworthy clock, the server also tracks a trusted time source so a licence cannot be revived by rolling a node's clock back. OmniWeb surfaces what is licensed and its health, the log of entitlement requests network functions have made, an on-demand query tool, and the server's live logs.
The License Server is a per-instance element page reached from the sidebar when one runs in the site's inventory, with a fleet view where several are deployed. All traffic goes through the OmniWeb backend proxy to the License Server's API, so it stays behind the single authenticated gateway. The documentation link in the page header (the in-context help button) opens this page. It is organised into tabs.
Overview / Status
A single-screen read of what the server is licensing and whether it is healthy. Summary cards give the count of total products, how many are valid and invalid, and the number of distinct licensees. A trusted time panel shows the state of the server's clock source — valid, grace period or invalid — because when trusted time is unavailable the server cannot safely validate licences at all, and that raises the page's health to a warning or error.
The Licensed Products table lists one row per licensed product, each showing the product, the licensee it is granted to, when it was issued, its start and expiry dates (with a "days remaining" or "expired N days ago" indicator that turns amber within 30 days of expiry and red once past it), and its valid/invalid status. Opening a row expands the full detail: the exact validity timestamps, whether the cryptographic signature is valid, any product metadata, and the signature itself. This is the quickest confirmation that the network's functions are all licensed and that nothing is about to lapse.
Request Logs
The audit trail of entitlement requests the network functions have made against the server. Each row records the timestamp, the source IP the request came from (which network-function host asked), the licensee and product it asked about, the decision — allowed or rejected — and, for a rejection, the reason. The list can be filtered by decision, by product, and by a partial source IP or licensee search, and it is paged. This is where you see, for example, that a newly deployed function is being rejected because its product was never licensed, or confirm that a function is successfully checking in.
License Query
An on-demand entitlement check. Enter a licensee and a product and the tool asks the server the same question a network function would — is this licensee entitled to this product right now — and returns the verdict: valid or invalid, the licence's valid-to date, the response timestamp, any metadata, and the signature. It is the direct way to confirm a specific entitlement without waiting for the owning function to check in, and it lists the known product identifiers (for example omnihss, omniupf, omnimme) so you can query the exact one.
Logs
The Logs tab tails the License Server's live log output for troubleshooting a single instance without leaving OmniWeb.
Related
- Every Omnitouch network function — the MME, HSS, DRA, PGW-C, UPF, SGW-C, SMSC, CSCF and the rest validate their entitlement here; each product's own Overview / Status tab shows a licence-health badge derived from this check.
- Operations Guide — back to the element index.