Zanzibar is Google’s consistent, global authorization system; a project started at Google in 2012. It primarily plays two roles. It acts as a storage system for access control lists and groups used by hundreds of Google projects (Maps, Google Drive, Calendar, and so on) to store permissions of digital objects. Also, Zanzibar acts as an authorization engine, where the Google products talk to check whether a given request is authorized or not.
At the moment Zanzibar manages 2 trillion+ tuples of 1500+ namespaces, replicated in several dozens of locations globally over 10,000+ servers. It handles 10million+ client queries per second.
This blog is the script of a talk I did internally at WSO2 in 2015 to inspire the team to build their personal brand. Found this today, buried in my Google Docs, and thought of sharing publicly (unedited), in case if someone finds it helpful!
Good Morning folks, thanks for joining in — it’s my great pleasure to do this session on ‘My Personal Brand is My Professional Success Story’.
First of all I must thank Asanka, Zai, Charitha, Usama and the entire marketing team for giving me the opportunity to present on this topic. In first sight, I thought…
In my previous blog, The Next TCP/IP Moment in Identity, I discussed why the enterprises will demand for developer-first IAM. As every company is becoming a software company, and starting to build their competitive advantage on the software they build, the developer-first IAM will free the developers from inherent complexities in doing Identity integrations.
The announcement came yesterday on Okta’s intention to acquire Auth0 for $6.5B, which is probably 40 times the Auth0’s current revenue, is a true validation of the push towards developer-first IAM. However, this is not Okta’s first effort towards developer-first IAM. In 2017, Okta acquired Stormpath…
Loved reading the book Ask Your Developer: How to Harness the Power of Software Developers and Win in the 21st Century by Jeff Lawson.
Jeff says in the book that every company is on a journey to becoming a software company and everyone is starting to see the world through the lens of software. He defines the term, software person. A software person is not necessarily a developer, it’s anybody who, when faced with a problem, asks the question, how can software solve this problem?
Build vs. Buy (or vs. Die)
In the book, Jeff takes the popular debate, build vs. buy, to another dimension; build…
We had our 35th Silicon Valley IAM meetup on 24th October to talk about HashiCorp Vault. Dan McTeer, the Strategic Technologist at HashiCorp and Bryan Krausen, a consultant on HashiCorp and AWS, presented in depth the Vault architecture and use cases, and took lot of questions from the audience.
Dan and Bryan are also the co-authors of the book, Running HashiCorp Vault in Production.
Companies and organizations have strategic decisions to make at the Customer Identity & Access Management (CIAM) front. First, they have to decide whether to invest into a dedicated CIAM solution or to build on existing infrastructure. If there is already a foundation, what should be their next steps to have a mature CIAM strategy in place? If they do not have a CIAM solution, where do they start? Applications, systems, identities tend to be siloed while as a business grows, it’s imperative they are cohesive and well-integrated in order to provide a superior customer experience.
An effective CIAM solution will…
The OAuth 2.1 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. The OAuth 2.1 specification replaces and obsoletes the OAuth 2.0 Authorization Framework described in RFC 6749.
The OAuth 2.1 specification consolidates the functionality in OAuth 2.0 (RFC6749), OAuth 2.0 for Native Apps (RFC8252), Proof Key for Code Exchange (RFC7636), OAuth 2.0 for Browser-Based Apps (https://tools.ietf.org/html/draft-ietf-oauth-browser-based-apps-07), OAuth Security Best Current Practice…
Customer Identity and Access Management (CIAM) over the time has become a bit of an overloaded term. There are multiple articles, blogs, analyst reports explaining what CIAM is and defining it in different ways. The objective of this blog is to provide my perspective of CIAM in one-line definition.
Before defining what it is, let’s be clear on why we need to worry about CIAM.
Why CIAM?
Transforming the customer experience is at the heart of digital transformation. Digital technologies are changing the game of customer interactions, with new rules and possibilities that were unimaginable only a few years back. …
WSO2 Identity Server ships with more than 35 connectors to support different authentication requirements. If you visit store.wso2.com, you can find all of them, and download and install into the product. Just like the product, all these connectors too, are released under the open source Apache 2.0 license.
Identity Server supports passwordless authentication with FIDO 2.0 — and mobile push based authentication with Duo and mePin. Also, we have partnered with Veridium and Aware biometrics to support biometric authentication. …
Speedle+ is a general purpose authorization engine. It allows users to construct their policy model with user-friendly policy definition language and get authorization decision in milliseconds based on the policies. It is based on the Speedle open source project and maintained by previous Speedle maintainers. Speelde was born at Oracle couple of years back, but didn’t get much community adoption. Both Speelde and Speedle+ try to address a similar set of use cases like the Open Policy Agent (OPA).
In our 31st Silicon Valley IAM meetup, we invited William Cai, the Speedle project lead and the founder of Speedle+ to talk about Speedle+. It was a very informative session, followed by an insightful demo. Please find below the recording of the meetup.
