Umbraco is an open source ASP.NET CMS with over 500,000 active installs worldwide and with more than 200,000 active community members. It was first released on February 16th 2005 and is still to this day an open source project backed by a commercial company.
The Umbraco CMS lets you do things your way by giving you full control of your website and its features. But it doesn't stop there.
We've built 3 unique products on top of the core features of our CMS to let you pick the one that fits your needs:
Umbraco Cloud is the perfect place for your Umbraco project with Azure Cloud hosting, automated upgrades and streamlined workflows to help you get the most out of your project.
Umbraco Heartcore is our headless CMS option with fully managed APIs, GraphQL support, CDN and much more.
Umbraco Uno is the low-code/no-code website builder that lets you build professional websites in no time - without needing a developer or worrying about hosting and upgrading.
Why use Umbraco?
Developers love it for its flexibility and scalability; it never gets in the way of your code and you can make your website look, feel and work exactly like you want it to. With an open source code and open APIs you can integrate, extend and scale your website to fit your needs.
Content is king. That's why've built features and workflows into the CMS that give content editors and marketers the best possible editing experience. Out-of-the-box they get a great editing experience, but what if you have specific requirements? Then your developers can customize the backend to fit perfectly to their needs.
Our main goal with Umbraco is to give you a platform where you have the freedom to do and manage things your way. Every project has different needs and requirements and instead of packing a system with options and buttons that may or may not be relevant for you, we’ve kept it neat and open.
- OIDC OpenID Connect is an extension to the OAuth standard that provides for exchanging Authentication data between an identity provider (IdP) and a service provider (SP) and does not require credentials to be passed from the Identity Provider to the application.
- SAML Security Assertion Markup Language is an open standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP) that does not require credentials to be passed to the service provider.
- SWA Secure Web Authentication is a Single Sign On (SSO) system developed by Okta to provide SSO for apps that don't support proprietary federated sign-on methods, SAML or OIDC.
- Attribute Sourcing
- Create Creates or links a user in the application when assigning the app to a user in Okta.
- Update Okta updates a user's attributes in the app when the app is assigned. Future attribute changes made to the Okta user profile will automatically overwrite the corresponding attribute value in the app.
- Deactivate Deactivates a user's account in the app when it is unassigned in Okta or their Okta account is deactivated. Accounts can be reactivated if the app is reassigned to a user in Okta.
- Sync Password Push either the users Okta password or a randomly generated password to the app. This feature is not required for all federated applications as user authentication takes place in Okta, however some apps still require a password.
- Group Push Push existing Okta groups and their memberships to the application. Groups can then be managed in Okta and changes are reflected in the application.
- Group Linking Link Okta groups to existing groups in the application. Simplifies onboarding an app for Okta provisioning where the app already has groups configured.
- Schema Discovery Import the user attribute schema from the application and reflect it in the Okta app user profile. Allows Okta to use custom attributes you have configured in the application that were not included in the basic app schema.
- Attribute Mastering The application can be defined as the source of truth for a full user profile or as the source of truth for specific attributes on a user profile.
- Attribute Writeback When the application is used as a profile master it is possible to define specific attributes to be sourced from another location and written back to the app. For example the user profile may come from Active Directory with phone number sourced from another app and written back to Active Directory.