Other | Nov 29, 2024 | 6 min read
Authentication doesn’t have to be a trade-off between security and usability. With Treblle 3.0, we bring you Single Sign-On (SSO), Multi-Factor Authentication (MFA), and Social Sign-On to secure your workspace effortlessly. Learn how these features make your team safer and more productive.
Authentication is a balancing act.
On one hand, you want to keep your data and systems safe. Conversely, you don’t wish for security measures to get in the way of your team’s productivity.
At Treblle, we’ve been thinking a lot about how to make this easier for you. With Treblle 3.0, we’ve introduced several key authentication features:
The aim is to make your workspace safer and accessible without compromising security or convenience.
This blog will introduce you to these new features, explaining how they work, why they’re essential, and how you can use them in your Treblle workspace.
Before jumping into how Treblle integrates these features, let’s quickly define them.
Single Sign-On (SSO) lets you log in once and access multiple applications or systems without needing to reauthenticate every time.
For example, if your team uses Okta or SAML, you can link it with Treblle to let users log in with their company credentials. This feature leads to no more problems of "forgot password” emails or manually managing account access for each teammate.
MFA adds an extra step to the login process, typically requiring something you know (like a password) and something you have (like a mobile authentication app).
This means that even if someone can grab your password, they still can’t get in without that second verification step, which adds a layer of protection.
Social Sign-On allows users to log in with existing accounts, such as Google or GitHub. It’s perfect for teams that prefer using existing credentials over creating new ones.
Now that you know the “what” and the “why,” let’s talk about the “how.”
NOTE: Only the workspace owner can access this setting.
Treblle Authentication Settings Page
Selecting Authentication Type inside Settings
This method ensures secure communication between Treblle and your provider.
Required fields inside SSO configuration
Testing SSO configuration
Logging in with SSO
Once you set up SSO, logging in is simple:
Login to Treblle account with SSO
Adding identifier
Adding an MFA is just as straightforward:
Multi-Factor Authentication inside Account settings
QR code and a password field needed for MFA verification
These steps ensure your workspace stays secure while being easy to access.
With Treblle’s new authentication features, security and accessibility go hand in hand.
Once you enable SSO in a Treblle workspace, team members can log in using their organization’s identity provider.
If someone switches between an SSO-protected workspace and a standard one, Treblle prompts them for extra authentication to ensure no one accidentally stumbles into areas they shouldn’t.
Layering MFA on top of SSO gives your workspace an additional shield.
For example, after logging in with SSO, a user might also need to enter a six-digit code from Google Authenticator before gaining access. This setup is simple and ensures an extra layer of protection.
Social Sign-On offers a quicker way for smaller teams or contractors to start. Instead of creating new accounts, team members can link their Google or GitHub accounts and get straight into the workspace.
By centralizing login credentials through SSO and adding MFA, you reduce the number of attack vectors for potential breaches.
With fewer passwords, there’s less risk of someone reusing weak or compromised credentials.
SSO simplifies onboarding and offboarding.
When someone joins your team, you don’t need to create accounts manually—just add them via your identity provider.
When someone leaves, revoke access at the provider level, and they’re automatically locked out of Treblle.
Only some people want to log in the same way.
Social Sign-On allows your team to pick what works best for them, whether that’s Google, GitHub, or traditional credentials.
To get the most out of Treblle’s new authentication options, keep these best practices in mind:
Treblle 3.0 introduces authentication features that secure your workspace without adding unnecessary complexity.
Whether using SSO for centralized login, MFA for added protection, or Social Sign-On for quick access, these tools are here to improve the developer experience when building your APIs and your team.
Try them out and let us know what you think. We’re always looking for ways to improve Treblle for developers like you.
💡
Ready to enhance your team’s security and productivity? Discover Treblle 3.0’s authentication features today and take control of your Treblle Workspace access with ease.
Treblle 3.0 simplifies API access management with the new Roles and Permissions feature. By defining users as Owners or Members, teams gain clarity over who can manage, edit, or view APIs and Workspaces. This ensures secure collaboration and protects critical data.
Attention spans are shorter than ever, and messaging needs to adapt quickly to stay impactful. For Treblle, this meant reevaluating how we present our value. Through careful reflection and evolution, we landed on a new identity that speaks directly to what we offer: the API Intelligence Platform.
In Treblle 3.0, we introduced Custom Alerts to help you stay ahead of API issues. Whether it’s error spikes, unusual activity, or performance concerns, Custom Alerts notify you instantly, keeping your team proactive. In this article, we’ll explore how this feature can transform your API workflow.