|
|
|
TSM App |
WebTSM Services API |
TSM .NET API (1) |
|---|---|---|---|---|
|
.NET Framework |
.NET 6 |
|
|
|
|
|
.NET 5 |
|
|
|
|
|
.NET Framework 4.8 |
|
|
|
|
Database |
Oracle (19c, 19c XE) |
|
|
|
|
Microsoft SQL Server 2019 |
|
|
|
|
|
Azure SQL |
|
|
|
|
|
PostgreSQL 16, 15, 14, 13, 12, 11 |
|
|
|
|
|
TimescaleDB (PostgreSQL compatibility required) |
|
|
|
|
|
Microsoft Office |
Microsoft Excel (2),(3) |
|
− |
− |
|
Microsoft Excel 365 (2),(4) |
|
− |
− |
|
|
Client/Server OS |
Microsoft Windows (3) |
|
|
|
|
Microsoft Windows Server (3) |
|
|
|
|
|
Azure Web App |
|
|
− |
|
|
Linux (not distribution-specific, see linux-x64 here: https://docs.microsoft.com/en-us/dotnet/core/rid-catalog#linux-rids) |
|
|
− |
|
|
Docker |
|
|
− |
Supported,
Not supported, − Not applicable
(1) The API is built on top of netstandard2.0. We recommend installing the latest .NET SDK available and supported by Microsoft.
(2) When installing Excel, make sure to add all available features and add-ins such as .NET Programming Support, and "Shared Office Features" to ensure full compatibility with the HAKOM TSM App.
(3) All versions with active mainstream support by Microsoft are supported.
(4) All Office 365 versions that are being maintained by Microsoft in the Semi Annual Enterprise Channels are supported.
WebTSM Services Authentication
Basically, any Identity Provider that supports the OpenID Connect Standard should be supported, however there are some discrepancies in how parts of the standard are interpreted by each vendor, so the support of specific features may vary.
The following table lists some popular (but not all) identity providers and their current support status.
|
Identity Provider |
Supported |
Tested |
Federation(1) |
OpenID Connect |
Known Issues/Limitations |
Configuration Guide Available(2) |
|---|---|---|---|---|---|---|
|
|
|
|
|
Only Basic authentication scheme supported. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"appid" claim in access token may have to be remapped to "sub" claim. Configuring other, external identity providers for federation has not been tested. |
|
|
|
|
|
|
|
Nested claims must be remapped in KeyCloak to be simple lists |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Currently, no ability to add custom claims such as roles. Only basic user profile is accessible through access token. Federation appears not to be a supported feature. |
|
|
|
|
|
|
|
Inclusion of custom claims in access_token could not be tested successfully. |
|
|
|
|
|
|
|
Does not support OpenID Connect. |
|
|
|
|
|
|
|
Only OAuth2.0 is supported. |
|
(1) Supports authentication through other providers. This would make it possible to use an identity provider with the HAKOM WebTSM Services which is not directly supported. Example: KeyCloak can allow users to sign in using their Facebook credentials, essentially making it possible to add Facebook Login to the WebTSM Services which is not supported directly (Facebook does not implement OpenID Connect at the moment) by putting KeyCloak inbetween.
(2) Configuring the HAKOM WebTSM Services for an external identity provider may require some additional configuration steps. For some providers, HAKOM has already prepared detailed step-by-step guides which are delivered either as part of our documentation or upon requests. Please contact HAKOM Support if you need additional assistance configuring your identity provider.
(3) Via Active Directory User Management