Updates for the security section

[rsill-neo4j]

There's more in the Security section. SoonTM

[rsill-neo4j]

^

[mjfwebb]

A decoded JWT is passed in to the context in a similar way that an encoded JWT is, but instead of using token, we use jwt, like this where the value of the jwt is passed in by code. customImplementation should be thought of as a placeholder for whatever the programmer would actually write.

const jwt = customImplementation();

const { url } = await startStandaloneServer(server, {
    listen: { port: 4000 },
    context: async ({ req }) => ({
        jwt: jwt,
    }),
});

Using jwt instead of token in the context informs the Neo4jGraphQL library that it doesn't need to decode it.

[rsill-neo4j]

adapted, thanks

[mjfwebb]

This isn't the case.

An encoded token also can be decoded via a JWKS endpoint.

[rsill-neo4j]

rephrased

[lidiazuin]

Thanks!! Left a few suggestions. It might be worth taking a look at the new section on admonitions in our style guide so you see the options we have besides note https://development.neo4j.dev/docs/docs-style-guide/content/formatting/#_admonitions.

[lidiazuin]

I think the way you rephrase it makes it sound like it's an option, but it may not be the case?

[rsill-neo4j]

True. Rephrasing

[lidiazuin]

Usually the index pages use a list with the name of the page and then a description, not incorporating the title within the description. It's not exactly a rule, but it's kinda consistent throughout docsets.

[rsill-neo4j]

oh.
well, this was my attempt to do something else with it, but it ended up pretty close to the original.
not a fan of these pages, since there's also the left side nav, which almost does the same, so the page doesn't serve much of a purpose.

but if it's a convention, then let's stick to it

[neo-technology-commit-status-publisher]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.