Authorization as a Service (feat. Jake Moshenko)

Authorization as a Service (feat. Jake Moshenko)

Jake Moshenko⁠, CEO of ⁠AuthZed⁠, discusses the importance of permissioning databases and the challenges of implementing permissions at scale. He explains how AuthZed solves this problem by providing a common API for flexible and fine-grained authorization. The target market for AuthZed includes companies of all sizes that need to add complex permission workflows to their applications. Jake demonstrates how AuthZed can be integrated with backend systems, web applications, and mobile apps. He also explains the benefits of using AuthZed, such as increased security and improved product velocity. The conversation concludes with a discussion on the AuthZed schema language and how permissions and roles are defined in the system. Jake Moshenko introduces the concept of permissions and relations in the context of access control. He explains how permissions can be granted to users for specific actions on resources, and how relationships between users and objects are defined. Jake also discusses the flexibility of defining roles and the granularity of permissions. He demonstrates how permissions can be visualized and edited in a user interface, and highlights the benefits of using a startup solution for access control. The conversation concludes with a discussion on the importance of leveraging existing tools and trusting innovative startups.

Takeaways

  • Permissions can be granted to users for specific actions on resources, such as read, write, and admin privileges.
  • Relations define the relationships between users and objects, allowing users to be readers, writers, or admins of a particular object.
  • Roles can be used to group multiple privileges or permissions together, providing a higher level of access.
  • Design time actions involve configuring the access control system, while runtime actions involve making API calls to enforce permissions.
  • When considering building or buying a solution, it is important to focus on core competencies and leverage existing tools and services.

Chapters

00:00 Introduction and Background

01:04 The Problem of Permissions at Scale

05:25 Implementing Authorization for Different Client Types

06:46 Integration with Backend and Web Applications

10:24 Implementing Permissioning for Mobile Apps

14:25 Benefits of Using AuthZed for Permissioning

22:00 Granting Access to Resources with AuthZed API

25:11 Defining Permissions and Roles in AuthZed

30:42 Introduction to Permissions and Relations

31:11 Understanding Permissions and Roles

32:20 Decoupling Relationships and Actions

33:36 Granularity of Permissions

34:14 Grouping Privileges into Roles

36:01 Design Time and Runtime Actions

36:46 Visualizing and Editing Permissions

39:33 Trusting a Startup

53:36 Building vs. Buying Solutions

58:36 The Value of Innovation and Trust

Jaksot(412)

Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?

Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?

Some of us prefer a framework that offers a lot more than what we might initially want, while others prefer a library that is small and simple but offers the barest minimum. Based on that simplified definition, what do you generally lean towards? #snowpal aws.snowpal.com learn.snowpal.com

24 Marras 202312min

Should you implement that next requirement now, later or never?

Should you implement that next requirement now, later or never?

Before you implement something, ask yourself if it needs to be implemented at all. #snowpal #softwaredevelopment #requirements Subscribe to our APIs on aws.snowpal.com.

17 Marras 20233min

Is GitHub Copilot worth it?

Is GitHub Copilot worth it?

I've been using GitHub Copilot for a few months now, and am ready to share my thoughts on it. #snowpal Subscribe to our APIs on aws.snowpal.com.

14 Marras 20234min

API Hubs. API Portal. API Platforms. What are some of the differences?

API Hubs. API Portal. API Platforms. What are some of the differences?

blobr, apiable, kong, and the list goes on... Let's understand the similarities and differences between some of the providers in the same space (of APIs). #snowpal Subscribe to our APIs on aws.snowpal.com.

14 Marras 20237min

How many developers does it take to build something?

How many developers does it take to build something?

That's a very generic question! So, let's take a hypothetical scenario and discuss that. #snowpal Download mobile app from ios.snowpal.com and android.snowpal.com.

14 Marras 20236min

What’s more difficult? Building something, or selling something?

What’s more difficult? Building something, or selling something?

Is it more difficult to build something than sell the same thing? Or, is it vice-versa? #snowpal Subscribe to our APIs on aws.snowpal.com.

14 Marras 20237min

Do not reinvent the wheel. Create what is not readily available.

Do not reinvent the wheel. Create what is not readily available.

To prove your Unique Selling Proposition to your investors and/or end users, you should build what is not readily (already) available. #snowpal Subscribe to our APIs on blobr.snowpal.com.

14 Marras 20239min

Backend as a Service: Leverage APIs where they are available to reduce Time to Market

Backend as a Service: Leverage APIs where they are available to reduce Time to Market

When would you be better served integrating a Backend as a Service as opposed to building one yourself? #snowpal Subscribe to our APIs on aws.snowpal.com.

14 Marras 20233min