Search Results :
×Easy and seamless access to all resources. ASP.NET Single Sign-On (SSO) via any existing SAML 2.0 Identity Provider
You can restrict your site to only logged in users by redirecting the users to your IdP if logged in session is not found
Allows a user to logout from all server sessions established via SAML SSO by initiating the logout process once.
Offers you to map the attributes from your IdP to your ASP.NET application
Map your Identity Provider roles to your ASP.NET application and restrict resources to specific roles
Add your own custom X.509 Certificate for sending signed Request and verification of signed Response.
Keep your IDP SAML Configuration and Certificates updated and in sync
Azure AD
Azure B2C
Okta
ADFS
Office 365
Google Apps
You can enable Single Sign-On (SSO Login) into ASP.NET using our ASP.NET SAML SSO module through any SAML-compliant identity provider. We have integrated with popular identity providers like Azure AD, ADFS, Okta, WordPress, Office 365, Google Apps along with several other identity providers.
Can't find your IDP ? Contact us on aspnetsupport@xecurify.com. We'll help you set up ASP.NET SAML Single Sign-On (SSO) in no time.
WordPress
Auth0
One Login
Keycloak
miniOrange
Shibboleth
There is an additional cost for the number of Identity Providers you have.
Need Help? We do offer technical support!
* We provide deep discounts on bulk license purchases and pre-production environment licenses. As the no. of licenses increases, the discount percentage also increases.
All of the payment methods listed below are supported by us. Payments can also be made through resellers. If you have a preferred reseller, we're happy to work with them.
Credit cards (American Express, Discover, MasterCard, and Visa) - If the payment is made through Credit Card/International Debit Card, the license will be created automatically once the payment is completed.
Please contact us
here
or drop an email at
aspnetsupport@xecurify.com
for more information
Please contact us
here
or drop an email at
aspnetsupport@xecurify.com
so that we can provide you the bank details.
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.
One (1) license will be sufficient for one application hosted on multiple servers behind a load balancer in load balancing environments. E.g. You’ve one (1) application running in a production environment, and the application is load balanced with two (2) servers behind load balancer. Here, only one license of the solution will be sufficient for you. Separate licenses are required to use the solution in other environments of the same application.
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
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.
Note: We recommend to install this library in your ASP.NET web application from NuGet store but in case you do not have access to the application source code or you are not a developer, you can proceed further with the Manual installation steps.
https://<your-application-base-url>/?ssoaction=config
Note: After installation of the plugin, we need to setup the trust between your ASP.NET application and your identity provider. SAML metadata is shared with identity provider so they can update their inbuilt configuration to support Single Sign-On.
There are two ways detailed below with which you can configure your SAML identity provider metadata in the module.
https://base-url/?ssoaction=login
<a href=”https://base-url/?ssoaction=login”>Log
in</a>
https://base-url/?ssoaction=logout
<a href=”https://base-url/?ssoaction=logout”>Log
out</a>
You can configure the ASP.NET SAML Single Sign-On (SSO) module with any identity provider such as ADFS, Azure AD, Bitium, Centrify, G Suite, JBoss Keycloak, Okta, OneLogin, SalesForce, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne, RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with your own custom identity provider. To check other identity providers, click here. Secure your ASP.NET MVC applications by performing Single Sign-On (SSO) into them. The miniOrange ASP.NET SAML 2.0 Connector supports C# and Visual Basic languages.
We also provide DNN SAML Single Sign-On (SSO) Connector. Click here to know more.
miniOrange also has modules for integrating with legacy applications like Active Directory, SiteMinder, Radius, Unix, and others. Using SAML, OAuth, OpenID, ADFS, and WSFED protocols, we can help you add login/authentication to your ASP.NET site.
Not able to find your identity provider? Mail us on aspnetsupport@xecurify.comand we'll help you set up SSO into ASP.NET with your custom IDP. For quick guidance (via email/meeting) on your requirement, our team will help you to select the best suitable solution/plan as per your requirement.