Connect identity and SaaS sources
Ask the business which vendors you use and you get a spreadsheet. Ask your identity provider and you get the apps people actually sign in to, who granted each one access, and what it is allowed to read. The second list is the one worth assessing, and these connections build it for you.
Every app or vendor they find becomes a vendor resource in Vendor Risk Assessment, waiting to be assessed. Discovery only records what the provider reports. Assessing a vendor is a separate step you start yourself.
Prerequisites
- A Dwaar role that holds
integrations:create. - Admin rights in the provider to create the read-only app, service app or service account its section below describes. For expense data, an export from your spend or accounting tool.
Connect a provider
- Open Integrations, choose the provider, then Add connection.
- Pick a Method if the provider offers more than one, and name the connection after the tenant or org it reads.
- Follow the guide beside the form to create the credential, and fill in the fields.
- Press Test connection. Dwaar signs in with these values, reads a little, and tells you what it can and cannot see before you can save.
- On the discovery step, look through Apps found. Each app shows how it was found, who consented, the data it reaches, its risky scopes and its users. For expense data the list is Vendors in the export, with each vendor's spend, payments, category and last payment.
- Choose All or Selected, add any exclusions, pick the frequency and save.
Dwaar only reads through these connections. The test tells you when a credential holds more than Dwaar needs, so you can narrow it before you save.
There is nothing to scan here, so these connections have Connection, Discovery and Activity tabs and no Scanning tab.
Okta
Okta offers two methods. Use the service app unless you cannot create one.
| Method | What you hand Dwaar | Why pick it |
|---|---|---|
| OAuth service app | The client id and private key of an API Services app. | Its token carries only the scopes you grant and belongs to no person. |
| API token | A token created by a Read-Only Administrator. | The fallback. The token acts with every permission of the admin who created it, and follows that admin's roles when they change. |
OAuth service app
- Sign in to the Okta Admin Console as a Super Administrator. Only a Super Administrator can grant Okta API scopes to an app.
- Open Applications and Resources › Applications, select Create App Integration and choose API Services. Name it, save it and copy its Client ID.
- On the General tab, under Client Credentials, set Client authentication to Public key / Private key, then Add key and Generate new key. Copy the private key before you close the dialog: Okta shows it once.
- Leave Require Demonstrating Proof of Possession (DPoP) header in token requests checked. Dwaar sends a DPoP proof with every request.
- On the Okta API Scopes tab, grant
okta.apps.readandokta.logs.read, and optionallyokta.appGrants.read. Grant no.managescope. - On the Admin roles tab, assign Read-Only Administrator. Okta asks for an admin role on every service app: the scopes say what the token may ask for, the role what it may see.
- Fill in the form and press Test connection.
| Field | Required | Value |
|---|---|---|
| Okta domain | Yes | Your org's address, such as acme.okta.com. The admin address, such as acme-admin.okta.com, works too. |
| Client id | Yes | The app's Client ID. |
| Key id | No | The key's kid. Only needed when you paste a PEM and the app has more than one key. |
| Private key (PEM or JWK) | Yes | The private key you copied. The JWK view carries the key's id; the PEM view is the same key without it. |
| Scope | What Dwaar reads |
|---|---|
okta.apps.read | The active apps and the people assigned to each. |
okta.logs.read | The System Log, for when each app was last signed in to over the last 30 days. Without it, last use stays unknown. |
okta.appGrants.read | The Okta API scopes each app holds, such as an app that can change your directory. Optional: without it the test says so and the rest works. |
Leave Settings › Account › Public client app admins off. It would make every service app a Super Administrator, including this one.
API token
- Pick an admin whose only role is Read-Only Administrator, ideally an account kept for integrations.
- Signed in as that admin, open Security › API, the Tokens tab, and select Create token.
- Set API calls made with this token must originate from to Any IP. A network zone that leaves out Dwaar's servers refuses the token's calls.
- Create the token and copy it. Okta shows it once.
- Fill in Okta domain and API token, then press Test connection.
The test says whose token it is, and warns when that admin holds more than Read-Only Administrator.
Okta revokes a token that goes unused for 30 days. Dwaar's daily discovery uses it, which keeps it alive, so leave discovery on. If the token is revoked anyway, create a new one and paste it with Replace credential on the connection's Connection tab.
What Okta adds
Each active app becomes a SaaS app, found as an SSO app, with the number of people assigned and its last sign-in. An app that holds Okta API scopes is also an OAuth grant. Okta's own apps, such as the Admin Console, are left out.
Microsoft Entra ID
Method: App registration. Dwaar uses an app in your tenant with three read-only application permissions and a client secret.
- Sign in to the Microsoft Entra admin center as at least an Application Developer. Open Entra ID › App registrations and select New registration.
- Name it, choose Single tenant only under Supported account types and select Register. On Overview, copy Application (client) ID and Directory (tenant) ID.
- Open API permissions › Add a permission › Microsoft Graph › Application permissions and add
Application.Read.All,Directory.Read.AllandAuditLog.Read.All. - As a Privileged Role Administrator or a Global Administrator, select Grant admin consent for your tenant. Each permission's Status then reads Granted for your tenant. A Cloud Application Administrator or Application Administrator cannot give this consent.
- Open Certificates & secrets › Client secrets, select New client secret, pick an expiry and copy the secret's Value, not its Secret ID. Entra never shows the value again.
- Fill in the form and press Test connection.
| Field | Required | Value |
|---|---|---|
| Directory (tenant) id | Yes | The Directory (tenant) ID, or the tenant's primary domain, such as acme.onmicrosoft.com. |
| Application (client) id | Yes | The Application (client) ID of the app registration. |
| Client secret | Yes | The secret's Value. |
| Permission | What Dwaar reads |
|---|---|
Application.Read.All | The enterprise apps, who is assigned to each, and the application permissions each holds. |
Directory.Read.All | The consents people and admins gave to apps. Application.Read.All does not cover them, and without this one, apps people consented to themselves are not found. |
AuditLog.Read.All | When each app was last signed in to. That report needs a Microsoft Entra ID P1 or P2 licence; without one, last use stays unknown. |
Add them as application permissions, not delegated ones: Dwaar reads without a person signed in. The delegated User.Read a new registration starts with is not used, and you can remove it. The test lists the permissions the app holds and warns if it also holds one that could change your tenant.
A client secret lasts at most 24 months. Before it expires, create a new one and paste it with Replace credential on the connection's Connection tab.
What Entra ID adds
A vendor is an app owned by another company, or a gallery, SAML or password sign-in app set up in your tenant. It is an SSO app when it signs people in or has people assigned, and an OAuth grant when it holds delegated scopes or application permissions. Microsoft's own apps, your tenant's own app registrations and managed identities are not vendors, so they are left out.
Microsoft 365
Method: App registration, with the same steps, fields and permissions as Microsoft Entra ID.
Apps from other companies in Microsoft 365, such as Teams apps, Outlook and Office add-ins and SharePoint integrations, reach your data through an Entra app and the consent given to it. So this connection reads them through the same app registration.
A Microsoft Entra ID connection to the same tenant finds the same apps. You need only one of the two, and connecting both does not double anything.
Google Workspace
Method: Service account. Dwaar uses a service account with domain-wide delegation, acting as one admin you name, within three scopes.
- In the Google Cloud console, pick or create a project your organization controls, and enable the Admin SDK API under APIs & Services › Library.
- Open IAM & Admin › Service Accounts and create a service account. It needs no Google Cloud role: what it may read is set in the Admin console.
- On the service account, open Keys, then Add key › Create new key, and choose JSON. The key file downloads.
- On the service account's page, select Show advanced settings and copy the Client ID under Domain-wide delegation. It is also
client_idin the key file. - As a super admin, open the Google Admin console at Security › Access and data control › API controls, select Manage Domain Wide Delegation, then Add new. Paste the Client ID and the three scopes, which the guide beside the form gives you with a copy button, and select Authorize.
- Fill in the form and press Test connection.
| Field | Required | Value |
|---|---|---|
| Primary domain | Yes | Your Workspace's primary domain, such as acme.com. |
| Admin to act as | Yes | The address of a super admin, or of an admin whose role may read users, their security settings and reports. |
| Service account key (JSON) | Yes | Choose the downloaded file or paste its contents, then delete the download. |
| Scope | What Dwaar reads |
|---|---|
admin.directory.user.readonly | The active users. |
admin.directory.user.security | Each user's OAuth tokens: the apps they granted and the scopes. |
admin.reports.audit.readonly | The token audit log, for when each app was last used over the last 30 days. Without it, last use stays unknown. |
Google has no read-only scope for tokens: admin.directory.user.security would also allow revoking them. Dwaar only lists them. A new delegation can take up to 24 hours to apply, usually much less.
Google refuses to create the key while the organization policy Disable service account key creation is on, as it is by default for organizations created since May 2024. An organization policy administrator can allow it for this project.
What Google Workspace adds
Each app people granted access to becomes a SaaS app, found as an OAuth grant. Google has no API for the Admin console's SAML apps, so those are not found. Google's own clients, such as Chrome and the Android and iOS account managers, are left out. Each discovery reads the tokens of at most 10,000 users.
Google gives no domain for an app, so a Google Workspace app is never placed under a vendor on its own. Link it yourself, as described in Apps without a domain.
Expense data (CSV)
Method: CSV export. Your spend tells you about vendors no identity provider sees, such as the ones people pay for with a card.
The file is the connection's credential. Dwaar stores it encrypted like a token and never shows it again.
- Export card transactions, expenses or paid bills from your spend or accounting tool as a CSV, one row per payment. Cover the whole period you want totals for, such as the last 12 months.
- Check the header row against the column names below, and rename a header cell if your tool names it otherwise. Case is ignored.
- Choose the file under Expense export (CSV). Dwaar reads it into the field and fills File name, which only labels the connection.
- Press Test connection. It says how many rows and vendors it found, and how many rows it skipped.
| Column | Required | Names Dwaar reads |
|---|---|---|
| Vendor | Yes | Vendor, Vendor Name, Merchant, Merchant Name, Payee, Supplier, Supplier Name, Description |
| Amount | Yes | Amount, Total, Spend, Cost, Net Amount, Transaction Amount, Amount (USD), Value |
| Date | Yes | Date, Transaction Date, Posted Date, Posted, Paid On, Payment Date, Invoice Date |
| Category | No | Category, Expense Category, GL Category, Expense Type, GL Account |
| Currency | No | Currency, Currency Code |
| Website or e-mail | No | Domain, Website, URL, Vendor Website, Email, Vendor Email |
Add the website or e-mail column if your tool has one. It ties each vendor to its domain, which is what joins it to the same vendor found through your identity provider.
Dates read best as 2026-10-31. 10/31/2026, 31.10.2026 and 31 Oct 2026 work too, but day-first dates with slashes, such as 31/10/2026, do not. Amounts may carry a currency sign, thousands separators, or brackets for refunds.
The file can be at most 900 KB, and Dwaar reads only the first 50,000 rows. If yours is larger, export a shorter period or keep only the columns above.
Rows naming one vendor become one vendor, with the sum of their amounts as its spend: by domain when any of its rows has one, else by name. Card prefixes such as SQ * are dropped from the name.
To update the totals later, upload a newer export with Replace credential on the connection's Connection tab. It adds the vendors it names and updates their spend and last payment. Vendors that only earlier exports named stay.
What you should see
After the first discovery, open Vendor Risk Assessment under Resources. It lists one row per vendor, not one per app.
One vendor per domain
An app whose domain is known belongs to the vendor of that domain. Slack found through Okta and Slack found through Google Workspace are two apps, but once both are tied to Slack's domain they sit under one vendor, and that vendor holds the assessments, tier and findings. An expense vendor with a domain is that same vendor.
The vendor shows what all its apps add up to: where it was found, the scopes and data its apps reach, and their risky scopes. Its user count is the largest from any one identity provider, named with that provider, with the others' counts beside it. Counts are not added up, because the same people sign in through several providers. The vendor's Overview lists its apps by identity provider.
Vendors belong to an organization. Two organizations connecting the same Okta tenant each get their own vendors, with separate assessments and findings.
Risky scopes
Dwaar reads each app's granted scopes and says what they reach and why that matters. Data it reaches groups them as Personal data, Customer data, Financial data, Source code, Secrets or Public only. Risky scopes gives a level and the reasons:
| Level | Rule of thumb |
|---|---|
| High | Reaches every mail, chat, meeting, file or cloud resource a person can open, or can change who signs in, what apps may do or roles. |
| Medium | Reads a whole area that is not content, such as the directory or calendars, or writes a narrow area, or sends mail. |
| Low | Signs a person in, or reaches only the app's own data or data an admin picked. |
The reasons read as Acts without a user, Changes the directory, Full cloud access, Reads mail, chat or meetings, Sends or changes mail or chat, Changes files, Reads every file and Long-lived token. A permission an app holds on its own, with no person signed in, raises its level one step.
A scope Dwaar does not know shows as n scopes not classified. It never lowers the level, and an app with one never reads as Public only. Unknown is not the same as harmless.
None of this is shown as critical. What an app could reach is a reason to look, not proof that anything went wrong.
Apps without a domain
An app the provider gives no domain for, which includes every Google Workspace app, stays its own vendor until you place it. Its Overview has a Vendor tile with the vendors its name suggests, from your other identity providers, your existing vendors and a list of well-known SaaS vendors. For example, an app named ChatGPT suggests OpenAI.
- Link to vendor places the app under a suggested vendor.
- Link to another vendor lets you pick any vendor of the app's organization.
- Unlink keeps an app apart from any vendor.
A name alone never links anything: a person always confirms. Dwaar keeps your decision for that app, and it wins over the domain in every later discovery. Linking needs resources:update on the app's organization.
Apps that disappear
An app the provider no longer lists, such as one an admin revoked, is kept and marked Missing at provider since the date it went. What you decided about its vendor stays, and its facts leave the vendor's totals.
When the test warns you
Most of these do not stop you saving. They tell you what discovery will not see.
| The test says | What to do |
|---|---|
okta.appGrants.read is not granted | Grant it on the service app to see which apps can change your directory. |
| The credentials cannot read the System Log | Grant okta.logs.read, or last use stays unknown. |
| The token acts as an admin with roles beyond Read-Only Administrator | Create the token as a Read-Only Administrator, or switch to OAuth service app. |
| The token carries no application permissions | Add the three Microsoft Graph application permissions and grant admin consent. |
| The app cannot read consent grants | Add Directory.Read.All and grant admin consent, or apps people consented to themselves are not found. |
| Sign-in activity is not readable | Add AuditLog.Read.All. Without a Microsoft Entra ID P1 or P2 licence, last use stays unknown. |
| The app also holds a permission that could change your tenant | Remove it. The three read permissions are enough. |
| The token audit log is not readable | Allow admin.reports.audit.readonly for the client id, or last use stays unknown. |
| Rows have no vendor or no amount and are skipped | Check the column names in the header row. |
| Rows have a date Dwaar cannot read | Use YYYY-MM-DD. Those rows give their vendors no last payment date. |
Try this next
Connect your identity provider and open Vendor Risk Assessment. Find the vendor whose apps reach the most with the least oversight: a High level, an admin consent, and a reason such as Reads mail, chat or meetings. If nobody on your team can say what it does with that access, open it and choose New assessment. Then add an expense export, and look for vendors you pay that no identity provider listed.