Skip to content
Discussion options

You must be logged in to vote

I think the best way would be to:

  1. Disable the built-in graphiql support with the dgs.graphql.graphiql.enabled property. Just to make sure you don’t run into weird conflicts between the built-in one, and your own.
  2. Add your own graphiql setup. This could be a separate module in your app, or just based on static resources like you already did.

Spring Boot, out of the box, serves files out of the static folder I believe, so you might not need any config, or you can further customize it with the standard SB features to work with resources.
You’ll find all the configuration options for graphiql itself in their docs.

If you “just” want to secure it; you might not not need any of this, but inst…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@SquireOfSoftware
Comment options

Answer selected by SquireOfSoftware
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants