Renabled Swagger for Intel

Task/intel 63388 intel apis

Author: mamtananavati

docs/Authentication.md

@@ -108,9 +108,7 @@ Successful responses include an access token and related fields. Below is an ill
 }
 ```
 
-The access_token in the response can be used to call Omnissa Intelligence APIs.
-
-On the **[REST APIs](REST-APIs.md)** page, the token panel above Swagger UI can use these service account credentials to fetch an access token and automatically populate Swagger's Bearer authorization for the Intelligence APIs. If the browser cannot call the auth endpoint because of CORS or network restrictions, obtain the token outside Swagger UI and paste the returned `access_token` into Swagger's Bearer auth input manually.
+The access_token in the response can be used to call Omnissa Intelligence APIs. When exploring endpoints on **[REST APIs](REST-APIs.md)**, paste the returned `access_token` into Swagger's **Authorize** button.
 
 ---
 

docs/REST-APIs.md

@@ -11,28 +11,4 @@ The Omnissa Intelligence (formerly Workspace ONE Intelligence) V2 API documentat
 
 Substitute your tenant’s regional **`api`** host name for examples that use hosts such as `api.sandbox.data.workspaceone.com`.
 
-<section id="swagger-token-bridge" class="swagger-token-bridge" aria-labelledby="swagger-token-bridge-title">
-  <h2 id="swagger-token-bridge-title">Get Access Token For Swagger</h2>
-  <p>Enter the service account credentials from your downloaded JSON file to fetch an access token and automatically populate Swagger's Bearer authorization for the Intelligence APIs.</p>
-  <form id="swagger-token-bridge-form" class="swagger-token-bridge__form">
-    <label class="swagger-token-bridge__field">
-      <span>Auth host</span>
-      <input id="swagger-auth-host" name="authHost" type="url" placeholder="https://auth.sandbox.data.workspaceone.com" autocomplete="url" required />
-    </label>
-    <label class="swagger-token-bridge__field">
-      <span>clientId</span>
-      <input id="swagger-client-id" name="clientId" type="text" placeholder="your-client-id@{tenant}.data.workspaceone.com" autocomplete="username" required />
-    </label>
-    <label class="swagger-token-bridge__field">
-      <span>clientSecret</span>
-      <input id="swagger-client-secret" name="clientSecret" type="password" autocomplete="current-password" required />
-    </label>
-    <div class="swagger-token-bridge__actions">
-      <button id="swagger-token-submit" type="submit">Get access token</button>
-      <p class="swagger-token-bridge__hint">If you already have a JWT, you can still use Swagger's <strong>Authorize</strong> button to paste it directly into Bearer auth.</p>
-    </div>
-  </form>
-  <p id="swagger-token-bridge-status" class="swagger-token-bridge__status" role="status" aria-live="polite"></p>
-</section>
-
 <swagger-ui src="intelligence-rest-api-swagger.json" />

docs/assets/javascripts/swagger-token-bridge.js

@@ -1,65 +1 @@
 /* Theme extras (stub for local builds when repo assets are incomplete). */
-
-.swagger-token-bridge {
-  margin: 1.5rem 0;
-  padding: 1rem;
-  border: 1px solid rgba(127, 127, 127, 0.25);
-  border-radius: 0.5rem;
-  background: rgba(127, 127, 127, 0.06);
-}
-
-.swagger-token-bridge > :first-child {
-  margin-top: 0;
-}
-
-.swagger-token-bridge__form {
-  display: grid;
-  gap: 0.75rem;
-}
-
-.swagger-token-bridge__field {
-  display: grid;
-  gap: 0.35rem;
-}
-
-.swagger-token-bridge__field input {
-  width: 100%;
-  padding: 0.65rem 0.75rem;
-  border: 1px solid rgba(127, 127, 127, 0.35);
-  border-radius: 0.35rem;
-  background: var(--md-default-bg-color, #fff);
-  color: inherit;
-}
-
-.swagger-token-bridge__actions {
-  display: grid;
-  gap: 0.5rem;
-}
-
-.swagger-token-bridge__actions button {
-  justify-self: start;
-  padding: 0.65rem 1rem;
-  border: 0;
-  border-radius: 0.35rem;
-  background: var(--md-primary-fg-color, #005eb8);
-  color: var(--md-primary-bg-color, #fff);
-  cursor: pointer;
-}
-
-.swagger-token-bridge__actions button:disabled {
-  opacity: 0.7;
-  cursor: progress;
-}
-
-.swagger-token-bridge__hint,
-.swagger-token-bridge__status {
-  margin: 0;
-}
-
-.swagger-token-bridge__status[data-state="success"] {
-  color: #0f7b0f;
-}
-
-.swagger-token-bridge__status[data-state="error"] {
-  color: #b42318;
-}

docs/assets/stylesheets/extra.css

@@ -5,8 +5,6 @@ hide:
   - toc
 ---
 
-{% if enable_swagger_openapi %}
-
 ![Omnissa Intelligence](assets/logos/favicon-dark.svg){ align=right }
 
 The Omnissa Intelligence (formerly Workspace ONE Intelligence) V2 API documentation describes how to query and extract data for use in other business intelligence tools. It also helps with building General Data Protection Regulation (GDPR) compliant tools and applications with REST APIs.
@@ -103,7 +101,7 @@ API calls to Omnissa Intelligence are always authenticated using a JSON Web Toke
 
 If access tokens are expired or invalid, the API invoked returns an HTTP status **401 (Unauthorized)**.
 
-Step-by-step credential setup is on **[Authentication](Authentication.md)**.
+Refer to **[Authentication](Authentication.md)** for step-by-step credential setup.
 
 ### API error handling
 
@@ -157,17 +155,3 @@ Refer to **Table 1. API Call Limits Per Organization** in the PDF for Standard,
 1. Follow **[Authentication](Authentication.md)** to configure a service account and retrieve tokens.
 2. Explore endpoints in **[REST APIs](REST-APIs.md)**.
 3. Compare payloads using **[Sample responses](API-sample-responses.md)**.
-
-{% else %}
-
-![Omnissa Intelligence](assets/logos/favicon-dark.svg){ align=right }
-
-The Omnissa Intelligence API documentation describes how to query and extract data for use in other business intelligence tools. It also helps with building General Data Protection Regulation (GDPR) compliant tools and applications with REST APIs.
-
-## Documentation and Reference
-
-| Name | Link |
-| --- | --- |
-| API Documentation for Omnissa Intelligence V2 | [Download PDF](https://developer.omnissa.com/omnissa-intelligence-apis/guides/DHUB-APIDocumentationforOmnissaIntelligence-V2-130326-183145.pdf){ .md-button } |
-
-{% endif %}