ResorsIT Usage on ResorsIT Tools Catalog

Native App

Mon, 01 Jan 0001 00:00:00 +0000

Native App

A Native App is a first-party application that runs only inside ResorsIT. It is built against platform internals and has no standalone existence outside the platform. Native apps are the only application type with direct access to the Resource Manager (RM); every other type reaches ResorsIT through the RUX external API.

What this means for a catalogued tool

Very few third-party tools are Native Apps – by definition a Native App is something built as part of ResorsIT itself (for example the platform’s own resource UI). A catalogued tool carries this label only when it is, or is becoming, a first-party ResorsIT component rather than an integrated third-party product.

Web App with SSO

Mon, 01 Jan 0001 00:00:00 +0000

Web App with SSO

A Web App with SSO is a web application that integrates with ResorsIT single sign-on, so users authenticate once (through the platform identity provider) and reach the app without a separate login. The tool supports OIDC or SAML, natively or through a plugin.

How ResorsIT integrates it

In platform terms a Web App with SSO becomes one of two application types, depending on where it runs:

Web App without SSO

Mon, 01 Jan 0001 00:00:00 +0000

Web App without SSO

A Web App without SSO is a web application that does not support single sign-on (no OIDC or SAML). ResorsIT still surfaces it, but only as a Link app: a bookmark tile in the Hub. Where the app has a login, users authenticate directly with it using separate credentials.

How ResorsIT integrates it

ResorsIT stores a URL and display metadata and shows a Hub tile
No identity flow with the platform identity provider
No reverse-proxy gating and no forward-auth
The tile can point at a self-hosted app or a public site – there need not be a login behind it at all

When a tool lands here

This label covers web tools surfaced as a plain tile with no platform-mediated login: public sites worth a tile, and interfaces that are neither federated nor placed behind the platform. If the app does support SSO, it belongs under Web App with SSO. If it is not a web app at all but is installed on a machine, see Deployment Payload.

Deployment Payload

Mon, 01 Jan 0001 00:00:00 +0000

Deployment Payload

A Deployment Payload is a tool that ResorsIT installs onto a desktop or a server, rather than integrating as a web app. The platform’s deployer ships it as a packaging artefact matched to the target host – for example an rpm or deb Linux package, a Windows installer, a Homebrew formula, a desktop bundle, or a container / Kubernetes payload.

How ResorsIT integrates it

The deployer places the software on a managed host and keeps it current
The tool runs where it is installed (agent, desktop app, CLI, or service)
Any identity or configuration is handled by the tool’s own mechanisms – though a tool that keys off the logged-in OS user is reached through a governed local host account

Precedence: only when the web modes do not apply

Some tools are both a web app and installable. Those are labelled by their web mode – Web App with SSO or Web App without SSO – because that is the primary way ResorsIT would adopt them. A tool is labelled Deployment Payload only when the web modes do not apply: command-line tools, desktop applications, agents, and background services that live on a host rather than being reached in a browser.

Device Class

Mon, 01 Jan 0001 00:00:00 +0000

Device Class

A Device Class entry is hardware, firmware, or an operating system – something ResorsIT treats as a device or platform to manage, not as an application to run. Operating-system distributions are the clearest example: a Linux or BSD distribution, or another OS, is the substrate other tools run on, not a tool you launch.

How ResorsIT integrates it

Managed as a host, appliance, or OS image rather than an app or a Hub tile
Provisioning, imaging, and lifecycle rather than SSO or a proxy route
Firmware and hardware appliances fall here too, where the “product” is the device itself

When a tool lands here

Today this label is applied mainly from the operating-system categories (Linux distributions, BSD operating systems, and other operating systems). Hardware and firmware entries also belong here. Software that merely runs on a device is classified by how that software itself is used – as a Web App, a Deployment Payload, or a Library.

Library

Mon, 01 Jan 0001 00:00:00 +0000

Library

A Library is a code library or SDK used inside software that a customer develops, rather than run as a standalone application. It is integrated at build or development time – imported into a codebase, linked, or called as a package – not deployed as a service or reached in a browser.

How ResorsIT integrates it

Made available to developers as a dependency, not hosted as an app
No Hub tile, no SSO, no proxy route of its own
Its value shows up in whatever application the customer builds with it

When a tool lands here

This label covers packages and frameworks whose purpose is to be embedded in other code. If a project ships both a library and a runnable application, it is classified by how the application is used – as a Web App, a Deployment Payload, or another mode – and the library aspect is noted in the evaluation.