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…
6 votes -
Support Geo Seach on Content Types
I work on a tourism website where many of our content types are tied to a Geographic location. We would like the ability to 'Geo Search' the graph but I understand this is not possible using content types (i.e. PageData, BlockData etc). I am to understand this is only possible using custom types.
1 - Can the Geo Search capability be extended to support content types (pages and blocks etc)?
2 - In the meantime, to avoid confusion, can the documentation (https://docs.developers.optimizely.com/platform-optimizely/docs/geo-search) be updated to reflect that this is only possible on custom types?4 votesThanks for sharing this idea. Our product and design teams are looking into it now. We’re exploring possible solutions and figuring out what implementation could involve. We are also actively currently updating our documentation. We’ll keep you posted here as things progress.
-
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 vote -
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.
3 votes
- Don't see your idea?