DEV Community: Peter Fernandez

CIAM Discovery Kit (Part 3)

Peter Fernandez — Tue, 02 Jan 2024 10:20:29 +0000

Happy New Year! Welcome to 2024!! 🎉 I’m never really quite sure what the etiquette is regarding wishing people a Happy New Year – particularly, when to stop doing it! 😂 As the year is still very much in it’s infancy, I feel I’m currently on safe ground here. But if I’m still wishing you a Happy New Year in a few weeks time, you certainly have my permission to call me out on it! 😉

Talking of infancy, I realised today that Discovery Kit is almost one month old! 🎂 Well, when I say almost one month old, I guess I mean it’s almost one month since it had it’s inaugural outing at React Day Berlin, and was “publically born” so to speak 😎 In CIAM Discovery Kit (Part 1) I introduced Discovery Kit, and in CIAM Discovery Kit (Part 2) I shared a little about my trials and tribulations during my experiments in decorating each NFC card with the artwork intended to deliver that “surprise” and “delight” experience at a booth. Here in Part 3, I’m going to turn my attention to talking more about the way I’m combining NFC and QR Codes, and the range of experiences that enables me to deliver.

To NFC or not to NFC? That was the question!

If you’re ever read My Journey of Discovery, you’ll know I’m a bit of a amateur thespian: Acting, Directing, or generally working backstage at my local theatre is quite often where I spend my “off” time. So I guess it’s not too surprising that I entitled this section based on a well known line from a Shakespear play 😂 Or at least some word-play variation along its lines 😉 But it is relevant. Why did I choose to use QR codes and NFC? What was the rationale behind that?

I knew I wanted Discovery Kit to be topic oriented and, as the intention was primarily to deliver a booth-related experience, I knew I wanted to create something tactile too: folks who come to a booth love the opportunity to pick things up and play with them 😎 So something colorful and eyecatching would fit the bill: helping to provide that “surprise” and “delight” element too. With my preference for reusing existing collateral – particularly when it comes to “colorful” and “eyecatching”; I’m really very far from being an artist 😳😂 – I was naturally drawn towards the idea of repurposing the Hero artwork as I described in Part 2. Logically then, the use of cards – something like playing cards or trading cards, which are often colorfully adorned – seemed appropriate. Cards also give the idea of something “collectable” – which in turn leads to possible opportunities for gamification, etc.

Throughout the latter half of 2023, my team did a lot of work with QR Codes. QR coding provides an easy way to access web based resources: a URL can be encoded in a QR Code, which can easily be scanned by a (personal) mobile device to provide access to a web page. As the objective of Discovery Kit is to enable visitors at our booth to easily access Discovery Content from a personal device, at scale, the use of QR Codes was something of a no-brainer.

QR Codes – even Dynamic QR Codes, where the encoded URL redirects to a second URL that can be changed on demand – are still essentially fixed quantities: once a QR Code is printed it cannot be changed! As a Developer Advocate at Auth0, I attended a lot of different events where different technologies are the main focus; some events focus on React development, whilst others focus on Python, Swift, .NET, Java and the like. Unless I intended to create multiple variants of each topic related card, I was going to have a hard time delivering any technology specific Discovery content using QR Codes. For instance, Auth0 provides a lot of SDKs, which are by their very nature inherently technology stack specific, and wven with Dynamic QR Codes it could easily get tricky. What if my Developer Advocate colleagues used Discovery Kit at the same time as me? Or what if Discovery Kit was used by someone for another Auth0 team, at the same time as any of us? Changing a Dynamic QR Code URL would change it for everyone as each Advocate, et al, would have the same copy of Discovery Kit. 🤔 There had to be a better alternative.

In a nutshell then, that’s how I came up with the notion of using NFC as well 😎 As it turned out it was a decision that would effectively address two aspects at once: I had cards on which I could print things, and I had a means to allow anyone with a copy of Discovery Kit to deliver technology specific URLs, dynamically, without affecting anyone else that was using it at the same time! Also, folks tend to find NFC novel, so the use of it adds to the “surprise” and “delight” element too 👍

NFC Cards are not all equal!

Did you know that there are a number of different types of NFC Cards? Well, I guess it’s more accurate to say there are a number of different types of NFC Chip. And not all of them work with all devices! That certainly came as news to me! 😳 Wak Dev – producers of the excellent NFC Tools – have a really useful knowledge-base article here, which lists the various NFC Chips and their degrees of compatibility.

If you recall from Part 2, I described one of my early encounters with NFC: the Mifare Cards produced by NXP. Mifare Classic chips are fairly low cost, even for the 4K ones. A lot of storage for relatively few 💵’s! Trouble is, they are only partially compatible across devices…read they don’t typically work out-of-the-box iPhones 🤦🏻‍♂️ They do typically work fine with Android phones, but that’s because NXP provide the software stack for Android devices, and include support for Mifare; Mifare format, it transpires, is not part of the NFC standard spec. I only discovered this after I’d placed an initial order of 50; fortunately it didn’t cost too much, but hopefully knowing this beforehand might prevent you, dear reader, from making a similar mistake! 🤗

Actually Mifare aren’t the only NXP cards that could potentially be problematic. There are some varients of the Desfire and Ultralight that could be a potential challenge too – as noted on the Wak Dev knowledge base article I mentioned earlier. At this point it’s also worth mentioning that there are manufacturers other than NXP who make NFC Cards/Chips. But NXP is arguably the most prominent by far.

I eventually ended up choosing NFC Cards using NTAG 216 Chips, which offer wide compatibility with a relatively large 868 byte storage capacity too. They can also be password protected – something which is extremely useful for preventing any “mischevious antics”, such as re-programming by someone using their mobile phone (NFC Tools which I mentioned above is available as both an iOS and and Android App, and makes programming an NFC Card with your mobile phone super-simple). I ended up sourcing these from the NFCTAGIFY store on Amazon. I would highly recommend these folks, as not only do they supply NTAG 216 cards at a reasonable price, they also don’t hesitate to ship replacements when the carrier “loses” a shipment in transit! 😳

QR Codes and NFC: the “dynamic duo” combo

As discussed, QR Codes are currently being used to provide access to topic-oriented Discovery Content in a topic-oriented fashion. At the moment, I must confess, I’m not using NFC for anything other than duplicating the topic-oriented URL that’s encoded in the QR Code printed on the NFC Card. Still, as I say, having NFC is a novelty so something this simple still provides significant value.

During my initial pilot at React Day Berlin I ended up using a version of Discover Kit where some cards had multiple QR Codes (see below). This ended up being, in part, by way of getting the kit ready for that particular event. Whilst it kind of worked (after a fashion), in truth it was confusing: folks had no idea which QR Code to scan, and the process of doing the scanning itself ended up being trickier than it needed to. I’ll be rectifying that by reverting those particular cards to having only QR Code (per side); in Part 2, I described how the use of stick-on artwork makes it easy to replace what’s printed on a card, so doing this should be a relatively straightforward process! 🎉

I may end up using NFC to reference the content previously access by the QR Code being removed. Of course that’s tricky in the above case, where two QR Codes need to be removed, but for the majority of the other cards it’s just the one that needs to go. My main intention though will be to use NFC to access technology-stack specific content that’s related to a particular topic. As I described earlier. I’ll be bringing Discovery with me to NDC London at the end of this month – stay tuned for more to come on that, and come visit our booth if you’re going to be there too 🤗 – and using Discovery Kit NFC would be ideal for providing access to any development updates on the likes of the React and .NET technology-specific SDKs developed by Auth0.

The future

As I was writing this installment, I came across these on Amazon; I was looking up the link to NCTAGIFY and Amazon kindly popped up with them as a suggestion. I’d already purchased a SENDEFN Credit Card Holder Purse and 80 Pcs Greeting Card Display holders – the former to provide easy transportation and the latter to provide some additional display options. I’ve provided some images below to illustrate all three. So it’ll be fun to see what I can do with my new purchase once it arrives.

In Part 4 I’ll take some more time tp share my thoughts regarding the direction NFC might take going forward. Actually I hadn’t intended a Part 4 to the CIAM Discovery Kit article at all, but whilst writing this installment I realised it would be advantageous to talk more speculatively for a change. About where Discovery Kit as a whole can go too, and not just the NFC aspect 😁

For now, let me wish you all a very happy and prosperous New Year, and leave you a parting shot of the tree giving it’s “last hurrah”! Enjoy 🤗

CIAM Discovery Kit (Part 2)

Peter Fernandez — Sat, 30 Dec 2023 19:09:19 +0000

In an interesting turn of events, the last few days of 2023 are bearing witness to something of a radical change in my personal life! It never fails to baffle me how, in the space of mere moments, a whole series of events can unfold that seem to take on a “life” of their own…and the result be so transformative. Sometimes for the good; sometimes for the bad. Sometimes seemingly bad, but actually for the best in the long run. That, I guess, is “life” as they say! 🤷🏻‍♂️😂

My current “life” adventure is, however, a tale for another time. But it is particularly apt by way of introduction here: Discovery – particularly the Discovery Kit – has been another transformative experience. Albeit one of a different nature. If you’ve read Part 1, then you’ll know why the CIAM Discovery Kit came about. Here in Part 2, I’m going to share a little more about the process I went through transforming the visual assets I used from a digital medium to a physical one 😎

So, in Part 1, I described a little about my idea to reuse some of the existing artwork that’s been used in numerous Auth0 Blog articles over the years. To help Discovery Kit deliver that “surprise” and “delight” experience at a booth. With the primary goal being to illustrate all of Auth0’s features in a topic-oriented fashion, and also easily provide folks with access to topic-cetric content too (ideally via a personal device), I want Discovery Kit to deliver assets that are both eyecatching and tactile.

Initial approach

My initial though was to take images like the ones below and get them printed directly onto NFC cards (more about the NFC aspect in Part 3). Surprisingly, finding someone to print NFC cards at a reasonable cost – well a reasonable cost for a small “prototype” batch at any rate – is not any easy task. Sure if I wanted a run of 100’s, then the economy of scale factors would bring costs down. But even then we’re talking about quite a lot of 💵 – especially for something where I had little to know idea how a print run might turn out 😳

I did, however, find a source that initially looked promising: https://www.plasticcardhub.co.uk/. As it turned out, these guys are actually pretty good. And they offer a service at a pretty reasonable price too; I’d have no hesitation in recommending them as a good third-party print shop. However, the NFC cards they supply (as part of their print service) turned out to be not quite good enough for what I had in mind: it turns out that Mifare cards are not part of the NFC range fully supported by the majority of mobile devices 🤦🏻‍♂️ You can read more about that particular “lesson learned” in Part 3.

Alternate approach

Back to the drawing board! 🤔 My next approach was to use Vistaprint – https://www.vistaprint.co.uk/. Again, a another really great online print service! They can print onto transparent stickers, which I reasoned I could then stick to the NFC cards (as you’ll read in Part 3, I eventually found some really suitable NFC cards that have turned out to be perfect for the job 😊). Cool 👍 And print costs were really reasonable too: creating a print run order of 10 different images on a 10-off basis (that’s 10 sheets per image, each sheet containing 12 stickers) also meant I could get free postage and packing! 🎉 Sadly though, the options provided by Vistaprint didn’t include dimensions that were a decent match for the size of the NFC cards and so, to put it bluntly…they looked sh**e once stuck on 😕

At this point it started to dawn on me that what I really needed was a way to experiment – i.e. make adjustments to the images and their sizes, all without going to an external print shop. What I needed was a way to print something myself, that could be easily transferred onto the NFC card. I did take a look at NFC card printers – which print directly on the surface of an NFC card – but decided the several hundred 💵 that was going to cost was a little out of my price range! 😂

Almost there

Whilst trawling Amazon, looking for inspiration, I came across Hayes Paper, Waterslide Decal Transfers. This stuff is pretty neat: you can print onto it using an inkjet printer and, after lacquering, submerge it in water and effectively slide whatever image you print onto the transfer surface. This has potential I though. It certainly fulfills my objective to be able to print myself and experiment, and an NFC card surface is certainly durable enough to be transferred onto. I ordered a pack up – along with a can of Rust-Oleum AE0040001E8 400ml (clear gloss lacquer) – and started to experiment. And quickly realized that this stuff is really designed for transfer onto curved surfaces (like mugs)! Bizarrely it’s really difficult to get it to transfer well onto something flat…and the size of an NFC card! 😳

Final approach

But the basic principal was sound: print onto something using my Inkjet and then transfer it on to the surface of the NFC card. Finally, after much searching I found: https://www.a4labels.com/product/transparent-inkjet-labels. This stuff is fantastic! And the Label Size that delivers 8 Per Sheet is perfect: just big enough to provide a print overrun margin, that you can then trim back using some scissors (and a little sandpaper) once you’ve stuck a printed label to the NFC card! Laminating using a clear matt finish lacquer – Rust-Oleum AE0040003E8 400ml – also gives the finished surface a more tactile feel.

And those inkjet labels are stickers, not transfers. Which makes them really easy to take off and replace – well, with a little White Spirit at any rate 😁 There’s likely to be quite a bit of that (label replacing) as I continue to experiment. I’ve only done one side of the NFC cards for the moment (never fear I have plans for the reverse 😉), and I assembled/formatted the printed images using a combination of Gimp and Pages. QR codes were generated courtesy of qr.io 😎

Next installment

In Part 3, I’ll talk more about the way I’m combining NFC and QR Codes to deliver a range of experiences. Well I’ll talk about what I’ve done so far on that front – and also what I’m planning to do going forward 😁 For now, let me leave you with a few shots I’ve taken whilst sat drinking coffee at Lyme Bay in Lyme Regis. Lyme is part of the Jurassic Coastline, not far from where I live. And it’s a perfect place to go when one needs some time to process life events…but doesn’t want to feel too alone whilst doing so! Enjoy 🤗

React Day Berlin: an inaugural outing for Discovery!

Peter Fernandez — Thu, 28 Dec 2023 15:27:03 +0000

As my last event of 2023, I recently got the opportunity to attended the in-person leg of React Day Berlin. As a Principal Developer Advocate at Auth0 by Okta, I spend a large portion of my time going to events like this, talking with Developers on all things Customer Identity & Access Management (a.k.a. CIAM). It wasn’t an event which I’d originally planned to attend, rather I was a last-minute substitute for a colleague who was unfortunately unable to make it. But boy, am I glad I was free to go! What an amazing high-energy opportunity to connect with such a fantastic group of folks!!

It wasn’t all plain sailing though 😳 Living as I do in the South West of England, I usually prefer to fly from Bristol, which is my local airport. As flying typically means I’m going to be visiting somewhere in Europe, flying from Bristol usually involves me going to Amsterdam or Copenhagen first. So I get to Bristol Airport in plenty of time and am sat waiting for my departure to Amsterdam. I’d already been informed that my onward flight from Amsterdam to Berlin had been cancelled: bad weather in Amsterdam is playing havoc with things at Schiphol Airport. And it wasn’t even certain if my flight from Bristol (to Amsterdam) would depart either 🥺 My (revised) plan was to get to Amsterdam and then catch a train to Berlin; trains from Amsterdam to Berlin were apparently still running, so that seems like a good option 😎 As I sat there I messaged the rest of my team to keep them updated…and it’s a good job I did! One of my colleagues pinged me to say that Deutsche Bahn have a strike planned! As I’m checking the train timetable – yep, sure enough, a train journey’s not going to cut it – the display board at the airport says my flight from Bristol…is now cancelled 🤦🏻 It was beginning to feel like I was in Planes, Trains And Automobiles! (a movie I’d highly recommend if you’ve never seen it); in the end I decide to hot-foot it to London Heathrow – read drive 3 hours – and take a direct flight to Berlin! That was a long day, I can tell you 😂

It was, however, definitely worth all the effort! Joined by one of my colleagues from the Auth0 Solutions Engineering team at Okta, I had a fabulous time connecting with Developers, Content Makers, co-Sponsors and the like. The GitNation team, who hosted the event, couldn’t have been more accommodating. And the team at Kosmos – the event venue – were ready and eager to help out with any eventuality.

We setup our booth (pictures above) in the hour before the doors “officially” opened. And were pretty much inundated the entire day (see the pictures below)! I love events like that: sure, I didn’t get to attend the talks I’d planned to, but there really wasn’t a dull moment!

What was also particularly exciting for me was that it was my first chance to showcase CIAM Discovery at an event, particularly the CIAM Discovery Kit which was there in a “pilot” outing. Discovery Kit, in particular, ended up being a real eye-catcher; something of a novelty one could say! Very much a “surprise” and “delight” attention grabber; both of which are bywords at a booth! Folks loved the artwork, and were intrigued by both the QR codes and the support for NFC, so much so that the content aspects of Discovery attracted some pretty healthy views as a result. There were some really great comments too, including the likes of “wow, this is so novel!” and “what an interesting concept; so colorful and fun!” We even had a few of the folks from the other booths come over and comment too!

If you’re a front-end developer, or even if you just get involved with the front-end as part of full-stack development et-al, and you get the opportunity to visit React Day Berlin in 2024…take it! You won’t be disappointed! 🎉

Discover secure access for GraphQL APIs: an AWS live-stream

Peter Fernandez — Wed, 20 Dec 2023 17:19:26 +0000

Recently, one of my colleagues invited me to an AWS live stream talk she was giving about building secure GraphQL APIs, using Auth0. She’s been doing a number of these AWS events of late – both live stream and in-person – and as this one was going to essentially be on the topic of Delegated Authorization, she asked me to come along and share some of my experience from an Auth0 perspective 😎

Auth0 – the SaaS platform that powers the Okta Customer Identity Cloud – is a great example of an off-the-shelf OAuth 2.0 Authorization Server. It isn’t the only one that’s out there, for sure, but it is one that I’ve been working with for more than 5 years now to deliver real value for developers 😄 In the context of OAuth 2.0, an (OAuth 2.0) Authorization Server is the thing that fundamentally enables a large part of the workflow behind Delegated Authorization.

What is Delegated Authorization?

Delegated Authorization is a mechanism that allows a third-party application to act on behalf of a user when accessing the protected resources for that user (typically via an API). Delegated Authorization also introduces the notion of Consent, where a user agrees to the Scope of access an application desires. In the case of OAuth 2.0, Delegated Authorization results in the generation of an Access Token which is typically consumed by an API as a Bearer Token. And an Access Token is typically generated by the Authorization Server upon successful verification of a users’ credentials (et al), using one of a number of “flows” – the most common being Authorization Code Flow and Authorization Code Flow with PKCE. You can discover more about Delegated Authorization, and what Auth0 provides to support this, at https://a0.to/do/apiz.

The thing wot we presented

I decided to present on three topics related to securing API access: Delegated Authorization, obviously, Attack Protection and Access Control; the latter I sub-divided into Role Based Access Control and Relationship Based Access Control. You can discover more about each of those other topics at https://a0.to/do/protect, https://a0.to/do/rbac and https://a0.to/do/fga respectively. Below are some screenshots of the slides I used as part of my presentation 😊

If you missed us live, then you can always catch our recording here on Twitch TV. I would highly recommend it, as my colleague – Pradheepa – goes into a really good demo of using both AWS AppSync and Amazon Bedrock! She definitely does the much more exciting part of the show! 😂

This was my first live-stream with AWS, and it was great fun to be part of. In fact, it was my first live-stream in quite some time! It’s always a pleasure working with Pradheepa, and Stuart – the show host from AWS – did a fantastic job at putting everyone at ease and setting the tone for the whole piece. I hope to do more of these in the near future, and from this one I will take away the following “fun” fact: I really need to invest in a better mic! 🤦🏻‍♂️

I hope you enjoy the recording, and I also hope you have a very enjoyable time over the festive season wherever you are 🤗

CIAM Discovery Kit (Part 1)

Peter Fernandez — Sat, 16 Dec 2023 18:00:22 +0000

As I write this, and for folks who celebrate it, that one particular day in the Christian calendar has once again come and gone. And with it comes the herald of an approaching New Year! But before we say a (fond) farewell to 2023, there’s still time for another delve into the CIAM box; a “Boxing Day” gift so to speak 😉

When I had the idea to build Discovery, my notion was that it would give me a consistent and repeatable way of connecting with Developers on all things Customer Identity & Access Management. And the plan, at least for phase one, was to be the creation of CIAM centric content; I’ve always envisioned the development of Discovery as a multi-phase effort, where new functionality and new assets (not just content) are released progressively over time. I knew I wanted to start by creating topic-centric content, because then I could talk about the challenges surrounding CIAM and relate back to how Auth0 can help.

Naturally, being web hosted, I knew I’d be able to create links and write posts (like this) that I could use to share the content I’d create. And syndicate to reach a wider audience. However, as I thought about it more, what I also began to realise was that I had a fantastic opportunity to leverage this topic-centric content in support of my role as a Developer Advocate at Auth0 by Okta too. For someone like me, who likes to “reuse” wherever possible, that’s a particularly interesting avenue to explore 😎

As a Developer Advocate I often get to attend events. And at these events I often find myself part of the team running a booth. I really love booth work 😊 Primarily because I get to talk to members of a developer community face-to-face and chat about all things technology. Even ease a pain point or two from time to time 🎉 When I’m at a booth people invariably come up and ask “So what is Auth0? What does it do?” These are folks who’ve never used the platform, and it’s often tricky to find an answer. Not because it’s hard to answer those sort of questions, but rather because Auth0 does so much! The benefit(s) it could bring to one scenario might not be the same as the one(s) it can bring to another. Articulating why using Auth0 is beneficial can be a challenge – particularly when one is only using words to paint a picture.

A picture, they say, is worth a thousand words. So instead of just using words what if there was a better way to pictorially visualize what Auth0 does and the benefits it can potentially provide. Topic-centric content is certainly a good way to provide descriptive narrative, but what would be really beneficial would be a way to illustrate each of those topics in a surprising and delightful manner (“surprise” and “delight” being bywords for delivering a really engaging and valuable experience at a booth)!

Over the years, some really eyecatching artwork’s been created that’s been part of numerous Auth0 Blog articles. Wouldn’t it be fun if I could take that artwork and bring it to life as something that folks could physically touch and interact with? At a booth, people love things that are both eyecatching and are tactile; all part of that “surprise” and “delight” philosophy. If I could create something visual (or, as it turned out, some things) that could be arranged to illustrate all of Auth0’s features in a topic-oriented fashion, and that folks could also use to access topic-cetric content too – ideally via a personal device – then wouldn’t that achieve my aim? Satisfying my desire to “reuse” too.

Well, to cut a long story short, that’s essentially how phase two: the CIAM Discovery Kit, illustrated below, was born! 🎉 For now I’ll leave you peruse the Discovery Kit assets at leisure. In Part 2 I’ll tell you more about how I transferred pieces of Auth0 artwork from their digital home to a physical medium, in order to create the eyecatching assets depicted below. And in Part 3 I’ll tell you more about how I combined the use of NFC and QR codes to provide visitors to our booth with dynamic access to Discovery content at scale using a personal mobile device.

Happy Discovery 🤗

Discovering CIAM

Peter Fernandez — Wed, 06 Dec 2023 20:28:00 +0000

Welcome to my CIAM Discovery blog! My name’s Peter, and this is my inaugural post 🎉

For those of you who may have read my blog post here, you’ll know that I’ve started to build a number of Discovery sites dedicated to my views on the things that I discover along my way. I decided to build not just one site, but rather a series of sites focusing on different subjects. And it all started because I felt I needed to share more about the things I’ve learnt – in the hope that some of it will be helpful to others.

But it’s not just about me being altruistic 😉 About 6 months ago, I made the move to the Developer Relations team at Okta, becoming a Principal Developer Advocate for all things Auth0. I’ve been working at Okta (and previously Auth0, before the acquisition) for a little over 5 and a half years, and for most of that time I’ve been a Solutions Architect – helping folks who’d purchased Auth0 integrate their products with the platform. As a Solutions Architect my job was to help customers integrate with Auth0; as a Developer Advocate, my job’s become more about educating (prospective) customers on all things CIAM, and how Auth0 can help.

Which brings us nicely back to my CIAM Discovery blog 😊 It’s my intention that this will become a vehicle for me to achieve two objectives in one fell swoop: share more about the things I’ve learnt in regards all things CIAM, whilst at the same time helping to build my community presence as an expert in all things CIAM/Auth0.

For the foreseeable future I shall most likely be focusing my attention on the mobile platforms – namely iOS and Android. I’ve been a developer for over 30 years, and have built everything from frontends to backends, embedded systems, kernel level modules, and several of the points inbetween. But I’m a relative novice when it comes to mobile development. So this is an exciting opportunity for me: discover a new horizon…leveraging a vista that is much more familiar – namely the world of CIAM 😎

I hope you’ll enjoy the journey with me. For now, let me leave you to browse the CIAM Discovery site, which sets the stage for the world of Customer Identity & Access Management. And perhaps you might discover how to enable safe, secure, and reliable CIAM in your application(s), by integrating with Auth0: the Software-as-a-Service (SaaS) platform that powers the Okta Customer Identity Cloud. Enjoy! 🤗