Sandrino Di Mattia (@sandrinodm) header
Sandrino Di Mattia (@sandrinodm) profile picture

Chief Product Architect @ Okta / Identity, Security, AI

Belgium
Joined September 2009
Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)Photo by Sandrino Di Mattia (@sandrinodm)
Sandrino Di Mattia retweeted
Replying to @okta
@okta is joining the S&P 500. It takes a lot of people working hard for a long time to reach a milestone like this, all in pursuit of our vision to free everyone to safely use any technology. I’m proud of our team and grateful to the customers and partners who put their trust in us. Thank you. We have a lot more to build. press.spglobal.com/2026-10-3…
20
13
5
235
23,274
New skill unlocked: generating clear and good looking diagrams, using your own brand. +200 examples of diagrams your agent can use as reference. sandrinodm.github.io/skills/…
7
2
2
51
11,489
Sandrino Di Mattia retweeted
everyone wants their product to work with AI agents. but no one wants their product to be abused. and let's be honest: AI means more + better "bad bots" we are building a product that can help you, by letting you verify there's a real human behind AI agents. we think it'll be really useful for: - dev products - e-ticketing - agent credit cards - social networks we are starting a private Beta of Human Principal with a few companies that want to integrate and give us feedback. interested? humanprincipal.ai
13
20
7
61
11,290
🚀 Just launched: aistandards.directory The ecosystem of agentic AI protocols and standards is expanding rapidly: MCP, A2A, AP2, XAA... Things are moving fast. This directory helps you keep up.
1
4
1
12
1,938
Sandrino Di Mattia retweeted
devs using @auth0 should be able to ask: "I want to create a mobile app with passkey and Google Sign-In, and access to an API with these scopes…" and we'd just set everything up for them with the new official @auth0 MCP server, you can 💪 @cursor_ai demo 📺👇, link in reply
14
29
6
340
45,286
Sandrino Di Mattia retweeted
Adding Authz to MCP can be this simple 🧵 fastify.register(fastifyAuth0API, { issuer: env.ISSUER, audience: env.AUDIENCE, }); That's what localden's #284 enables. Here is a prototype: github.com/ciamshrek/mcp-aut…. How does this work, What’s next? Read On ⬇️ (1/N)
3
3
3
16
2,172
Sandrino Di Mattia retweeted
✨ Agents can now act as MCP Clients ✨ New auth integrations for your MCP Server with Stytch, Auth0, and WorkOS ✨ Hibernation for McpAgent so you only pay when your agent is working ✨Durable Objects on FREE tier means you really have no excuse for not building agents now
5
19
2
180
17,411
Sandrino Di Mattia retweeted
Replying to @tweetsbycolin
👋hey Colin. This is an important and nuanced topic. Let's dive in 👇 There’s different types of applications where refresh tokens are used: - Regular Web Applications (eg: PHP/Express/Next.js w/ App Router). These can access cookies server side and will mostly just need a session. If a refresh token is needed, it can be stored in a database, in the session or in an HttpOnly cookie - BFF apps (eg: Next.js w/ Pages): Same - Mobile Apps: Can store refresh tokens in the Keystore where it’s safe - SPAs: related to this SDK There is a recently published BCP related to this: OAuth 2.0 for Browser-Based Applications ietf.org/archive/id/draft-ie… co-authored by @aaronpk from our team. It goes into detail about the various architectural patterns available for JS apps and the attacks that are mitigated with each pattern.. Now, for this specific case: our initial guidance was indeed to not store refresh tokens and instead use what we refer to as Silent Authentication. This leverages the OIDC Authorization Code Flow (with PKCE) + an iframe to renew tokens using a session (this session is stored in an HttpOnly cookie). This works as long as all of your applications (and your Auth0 tenant) are on the same parent domain. Modern browser versions have implemented several kinds of Third Party Cookie blocking which will break this flow when multiple domains are involved. Few examples: 1. car-rental.com interacting with car-rental.auth0.com (seen as third party) 2. dev-car-rental.vercel.app interacting with login.car-rental.com (seen as third party) 3. car-rental.com interacting with login.car-rental.com configured as a custom domain (this is ok, seen as first party) 4. car-rental.com and car-deals.com interacting with login.car-rental.com (car-deals.com is seen as third party). For those scenarios, in which access tokens are needed on the client side, we recommend using refresh tokens as the mechanism to renew tokens. Client side logic running in the browser can be vulnerable to XSS, so we must be extremely careful here. This is why we’ve implemented the guidance from the OAuth 2.0 Security BCP (datatracker.ietf.org/doc/htm…) and OAuth 2.0 for Browser-Based Applications BCP section 6.3.2.3 (ietf.org/archive/id/draft-ie…) related to using refresh tokens on the client side (expiration + rotation). We are also working on introducing token binding, also part of the BCP spec datatracker.ietf.org/doc/htm…, limiting the use of those refresh tokens to the browser they were issued to. As part of that work we can now detect if refresh tokens have been leaked and revoke that refresh token when that is the case. We also wrote a blog post about this at the time auth0.com/blog/securing-sing…. It’s only after we introduced this feature that we could provide guidance to use these from the client side. I think it might be worth clarifying a few things 1. The current OAuth spec doesn't define a session token and we have no concept of it. There’s sessions (which are HttpOnly cookies), id_tokens, access_tokens and refresh tokens. They are very different artifacts and have different uses, limitations and security controls. They should not be conflated in “session tokens”. 2. OWASP talks about session identifiers, not about session tokens (see point 1). github.com/OWASP/CheatSheetS…. We are an OAuth and OIDC Authorization Server and implement the security guidance outlined in the OAuth 2.0 Security BCP to make sure these refresh tokens are protected. 3. React is used in SPAs, Mobile Apps, Server Rendered apps, BFFs. The architecture of the application in which React runs matters. There isn’t a one size fits all for React.
1
2
2
18
4,769
Sandrino Di Mattia retweeted
our free plan @auth0 just got a huge boost: - 25k MAUs - custom domains - passwordless logins and more... if you are starting an app, this is for you
25
35
11
338
62,041
Sandrino Di Mattia retweeted
seems GoDaddy is now using @OpenFGA for authorization. proud to see such a company leverage an OSS project I created for such an important capability godaddy.com/engineering/2023…
4
18
2,182
Sandrino Di Mattia retweeted
Vittorio Bertocci was a force to be reckoned with, leaving an indelible mark on the identity industry and capturing hearts along the way. Unforgettable. Remarkable. Impactful. 💙 auth0.com/blog/in-celebratio…
10
99
12
387
38,382
Sandrino Di Mattia retweeted
Hey #dotnet friends, are you interested in writing some articles for Okta? We'd love to pay you🤑and everything. There are lots of topics to cover in this community and I need help doing it!
16
28
2
92
Sandrino Di Mattia retweeted
Excited to announce something we've been working on this year with @Auth0Lab team: A Google Zanzibar-inspired service to solve fine-grained authorization at scale, for all your applications. Quick video walkthrough of the dashboard and 🧵
10
9
4
68
Sandrino Di Mattia retweeted
With the rise in remote work, Zero Trust security grew tremendously in the past year. That’s not changing anytime soon. Our State of Zero Trust Security report looks at how organizations around the world are approaching Zero Trust – check it out ⬇️ + ➡️ https://teapaw.org/t.co/tY0xiPuHWJ
1
4
1
16
Sandrino Di Mattia retweeted
Today we enter a new stage in our journey at Auth0 🚀 . The deal with Okta is closed! We declined several acquisition offers over the years, including a handful from Okta. So why did we say yes this time? Thread 🧵
7
54
11
395
Sandrino Di Mattia retweeted
I co-founded @auth0 with my brother-in-arms, @woloski. Today, we start a new chapter partnering with @ToddMckinnon and his team. Proud and excited to join forces with @Okta. auth0.com/blog/okta-acquisit…
9
44
11
414
Sandrino Di Mattia retweeted
We are launching the Auth0 CLI today! This was a project that came out of a hackauth0n ✪ in January and the team continued working on it on Fridays. They are launching it as experimental release to get feedback! github.com/auth0/auth0-cli Demos on the thread 👇🏻 🧵
1
16
1
57
Sandrino Di Mattia retweeted
We just released Auth0 Organizations! What is it? A new entity in the Auth0 model to allow teams (enterprises, partners, vendors, etc) to access your product, removing a lot of heavy lifting for developers. 🧵
2
6
1
37
Sandrino Di Mattia retweeted
I am very excited to share that @okta signed a definitive agreement to acquire @auth0. I believe that Okta and Auth0 have an incredible opportunity to build the identity platform of the future *faster*, and make the internet more secure for everyone.
53
76
30
777
Sandrino Di Mattia retweeted
We are very excited to share that we will be joining forces with @Okta. Learn more here. https://teapaw.org/t.co/wv8Uva16AP
17
162
42
555