Remove an application's logo
The tile goes back to its EZGH product's mark or its monogram. No logo is 404.
https://sso.ezghcloud.com/v1/organizations/{orgId}/sso/applications/{appId}/logoAuthorization
Path parameters
Returns
200
The application, with logoUrl null.
- logoUrlstring | nullrequired
Read-only: where sso-edge serves the application's uploaded logo (its portal tile's icon) on the directory's host, https://.sso.ezgh.app/branding/applications//logo?v=…, or null. A replaced logo is a new URL. Upload it with PUT …/applications/{appId}/logo; create and update refuse logoUrl.
format: uri - managedBystring | nullrequired
The EZGH product that manages this ezgh application through its own internal routes (MCP Central's, created when EZGH SSO is associated with it), or null. A managed application is read-only here: updating or deleting it, or changing its assignments, is 409 managed_by_product, and creating another ezgh application of its product in the directory is refused the same way.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.