SAML Single Sign-On for ASP.NET Applications

Yes, we provide 24*7 support for all and any issues you might face while using the plugin, which includes technical support from our developers. You can get prioritized support based on the Support Plan you have opted. You can check out the different Support Plans from here.

miniOrange does not store or transfer any data which is coming from the Identity Provider to ASP.NET. All the data remains within your premises /server.

Multiple IDP support allows you to enable authentication on your site from multiple IDPs. For example - If your users exist in Azure AD as well as Okta, then you can opt for the multiple IDP Plugin and allow user authentication from either IDP. We support SSO authentication from multiple Identity Providers in our Enterprise and Premium versions of the plugin.You can add multiple IDPs to your license at $100 per IDP. Please reach out to us at aspnetsupport@xecurify.com

If you have multi-tenant architecture in your .NET application, you can manage SSO settings for each specific tenant with this feature.

Licensing for miniOrange plugins/modules/connectors is application instance-based and linked to the Fully Qualified Domain Name (FQDN) / unique URLs of the application(s). ‘Application implies an instance of software that is hosted and run on a server. E.g. If you have separate apps for different purposes, both of these applications can be accessed with any one type of FQDN shown below: 1. domain1.com and domain2.com OR 2. app1.domain.com and app2.domain.com OR 3. domain.com/app1 and domain.com/app2 OR 4. test.domain.com/app1 and test.domain.com/app2 You’ll be required to have two separate licenses for each application. With pre-production environments (staging, user acceptance testing, and testing), you'll need separate licenses for each.

We do not provide the developer license for our paid plugins and the source code is protected. It is strictly prohibited to make any changes in the code without having written permission from miniOrange. There are hooks provided in the plugin which can be used by the developers to extend the plugin's functionality.

The plugin licenses are subscription based and you have to pay annually.

Yes, we have an instance-based licensing policy. The plugin's licensing is linked to the domain of the .NET instance. Thus, if you have a dev-staging-prod environment, you'll need three licenses (with discounts applicable on pre-production environments). Additionally, If you need to transfer a license to a different domain, you can deactivate it from the current domain and activate it on the new one.