4 results found
-
Access to graphiQL
Hi Team,
The default GraphiQL dashboard operates on a single key principle, which means it lacks authentication mechanisms. Consequently, even if the consuming team implements the OIDC feature for authenticating graph usage, this authentication cannot be enforced when accessing the graph through the dashboard. As a result, "Read" access is granted universally, rather than being restricted to specific groups.
Implementing authentication for graph usage, potentially through the Identity Provider (IdP) that users log in with, would significantly enhance security. This approach would ensure that content is not universally accessible and is only available to authorized products, effectively "hiding" it from…
7 votesWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
PaaS Portal - Delete cached content also deletes Graph Cache
There should be a button (or by clicking the CDN-cache purge) that cleares/invalidates the Graph cache.
This is especially useful (necessary) when Graph synchronization fails, as the cache is only cleared upon sync completed.1 vote -
graph indexing
Request: ability to trigger Graph indexing job programmatically
If you update content types via import or API, my understanding is that you need to manually trigger the Optimizely Graph indexing job to sync those model changes to Graph.
The ability to trigger that indexing job via API would enable more automated processes for introducing changes to content types to a SaaS CMS instance.
1 voteWe’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!
-
Inconsistent trailing slash behavior with Simple Address in SaaS CMS + Content Graph
I'm encountering an inconsistency when working with URLs in the SaaS CMS frontend using Content Graph. All content URLs returned from Graph include a trailing slash except for those using the Simple Address feature — see screenshot for reference.
This inconsistency makes it difficult to reliably match URLs when resolving routing on the frontend. Since URL comparison often involves exact string matches, the mismatch in trailing slash behavior leads to additional logic and potential edge cases.
4 votes
- Don't see your idea?