<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Token on Work In Progress</title><link>https://www.pm50plus.co.uk/tags/token/</link><description>Recent content in Token on Work In Progress</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pm50plus.co.uk/tags/token/index.xml" rel="self" type="application/rss+xml"/><item><title>Token for auth with GraphQL for AuraDB</title><link>https://www.pm50plus.co.uk/post/2025-05-23-graphql-jwks-part-2/</link><pubDate>Fri, 23 May 2025 00:00:00 +0000</pubDate><guid>https://www.pm50plus.co.uk/post/2025-05-23-graphql-jwks-part-2/</guid><description>&lt;h1 id="an-introduction-to-using-jwts-with-graphql-for-auradb---part-two"&gt;An introduction to using JWTs with GraphQL for AuraDB - Part Two&lt;/h1&gt;
&lt;p&gt;In &lt;a href="https://www.pm50plus.co.uk/2025/05/16/graphql-jwks-part-1.html"&gt;part one&lt;/a&gt; I covered how to set up GraphQL for AuraDB to use JWTs and the identity provider, okta, that generates them.&lt;/p&gt;
&lt;p&gt;This blog will look at using properties of a token to control access to the API and the data within.&lt;/p&gt;
&lt;p&gt;But I&amp;rsquo;m overreaching a bit as I&amp;rsquo;m assuming knowledge ( a trap so easier to stumble into when trying to convey information ) on the topic of JSON Web Token (JWT ).&lt;/p&gt;</description></item><item><title>Using token with GraphQL for AuraDB</title><link>https://www.pm50plus.co.uk/post/2025-05-16-graphql-jwks-part-1/</link><pubDate>Fri, 16 May 2025 00:00:00 +0000</pubDate><guid>https://www.pm50plus.co.uk/post/2025-05-16-graphql-jwks-part-1/</guid><description>&lt;h1 id="an-introduction-to-using-jwts-with-graphql-for-auradb---part-one"&gt;An introduction to using JWTs with GraphQL for AuraDB - Part One&lt;/h1&gt;
&lt;p&gt;There are two options ( we&amp;rsquo;re looking at another token based approach for the future ) to control access to a GraphQL for AuraDB endpoint&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;API Key&lt;/li&gt;
&lt;li&gt;JWT&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Using APIs keys are asimple, straight forward approach to control access to a GraphQL API and work really well for development environments. For production environments we recommend the use of a 3rd party indentity provider that manages tokens in the form of JWTs as these provide more flexibility when securing access to your GraphQL. Additionally, JWTs enable the use of rules within your type definitions for authentication and authorisation.&lt;/p&gt;</description></item><item><title>Applications, Tokens and Neo4j Query API</title><link>https://www.pm50plus.co.uk/post/2024-10-24-app-token-query-api/</link><pubDate>Thu, 24 Oct 2024 00:00:00 +0000</pubDate><guid>https://www.pm50plus.co.uk/post/2024-10-24-app-token-query-api/</guid><description>&lt;h1 id="applications-tokens-and-neo4j-query-api"&gt;Applications, Tokens and Neo4j Query API&lt;/h1&gt;
&lt;h1 id="using-tokens-with-applications-and-neo4j-query-api-for-auth"&gt;Using tokens with Applications and Neo4j Query API for auth&lt;/h1&gt;
&lt;p&gt;In a previous blog post I discussed a web application obtaining and using a token with Neo4j Query API as a result of a user successfully authenticating. This entry looks at what would be involved for an application to obtain a token and use it with Neo4j Query API.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Plot spoiler&lt;/strong&gt; - it&amp;rsquo;s very similar.&lt;/p&gt;</description></item><item><title>Dipping into the code from the trinity of SSO, Neo4j and a web application</title><link>https://www.pm50plus.co.uk/post/2024-10-17-token-query-api-the-code/</link><pubDate>Thu, 17 Oct 2024 00:00:00 +0000</pubDate><guid>https://www.pm50plus.co.uk/post/2024-10-17-token-query-api-the-code/</guid><description>&lt;h1 id="commentary-on-the-web-application-code-used-in-sso-post"&gt;Commentary on the web application code used in SSO post&lt;/h1&gt;
&lt;p&gt;As a follow on from my previous blog post, the trinity of SSO, Neo4j and a web application, this entry takes a deeper look at the code used for the web application to see how it all fits together.&lt;/p&gt;
&lt;p&gt;Given my JS / React knowledge is basic ( and I&amp;rsquo;m flattering myself there ) the more experienced of you are likely to be amused at my efforts.&lt;/p&gt;</description></item><item><title>Using token with Query API - an example with SSO</title><link>https://www.pm50plus.co.uk/post/2024-10-16-token-query-api/</link><pubDate>Wed, 16 Oct 2024 00:00:00 +0000</pubDate><guid>https://www.pm50plus.co.uk/post/2024-10-16-token-query-api/</guid><description>&lt;h1 id="the-trinity-of-sso-neo4j-and-a-web-application"&gt;The trinity of SSO, Neo4j and a web application&lt;/h1&gt;
&lt;p&gt;Consider a web application that consumes data from Neo4j. This will require the web application to authenticate and retrieve that data using credentials that are accepted by Neo4j. If our users needed to remember one set of credentials for the web application, another set for Neo4j and then enter those at the correct moment, it&amp;rsquo;s going to be a jarring user experience.&lt;/p&gt;</description></item></channel></rss>