I have been trying to implement a Drupal 9 Commerce site with Opayo (previously Sagepay) as a payment gateway. The site was working up until Monday when the EU Strong Customer Authentication (SCA).
Opayo have said
You are using PI integration but its on protocol 3- it must be upgraded to protocol 4 to be compliant for 3D Secure V2 (SCA).
Does anyone have a Drupal 9 Commerce Opayo site that has PI integration with protocol 4.
Would you possibly tell me how you implemented this.
Many thanks for your help.
N
Related
Our clients were suddenly unable to connect to our backend on Heroku since August 2nd. They all use a Windows 7 or Windows 10 cash register device.
Apparently the cash register software that implemented our API doesn't support TLS1.2. And we didn't receive any notification from Heroku that legacy versions of TLS would be EOL.
We have solutions in progress (migrating to AWS or the 3rd party implementing TLS1.2), but they will take some time and my boss would love to have it solved by today.
Is there a possibility to force TLS1.0/1.1 via the Heroku CLI?
I'm trying to figure out the right architecture from a mix of current .NET authentication/authorization offerings. One question that I haven't been able to find much online information on: What are the benefits of having ThinkTecture IdentityServer 2.0 federate ADFS 2 (which is authenticating domain users using Active Directory credentials), vs having IdentityServer authenticate users against the domain directly?
For my company, I see only 3 possible requirements for ADFS 2, but I'd prefer to avoid installing it if IdentityServer is sufficient (mainly because it's open-sourced, and therefore more readily debuggable, extensible, and understandable):
Claims-based authentication of corporate (Active Directory) users.
Support for Office365 SSO - there are directions for integrating Office365 with ADFS
Federating external (business partner) ADFS services (we don't currently need this, but I'd like to keep the option open)
Is any of this functionality not provided by, or not easily added to, IdentityServer 2.0?
Well IdSrv does not do Windows authentication out of the box. It would be easy to add forms based authentication for AD users - but Windows integrated (SSO) would be more involved.
IdentityServer is a really good product but:
Only authenticates against SQL not AD
Doesn't have SAML support - useful for third party integration e.g. SalesForce
No rich claims rules language
which ADFS does for you.
#leastprivilege answered the first - the rest are definitely not trivial to add.
Don't have much experience with Office 365 but it sits on top of Azure Active Directory which can be hooked up with IdentityServer - refer Federating IdentityServer with Windows Azure Active Directory.
Windows Server 2003, IIS 6
We have an ASP.Net application, which is accessed using HTTP by customers.
Now one customer wants to access this application, using HTTPS (company security rules).
Can I set up IIS 6, so that I can satisfy both requirements? So that regardless of typing
http://www.foo.com/bar or https://www.foo.com/bar, the users will get the same experience? And those using HTTPS will continue using HTTPS during their ASP.Net session?
I have a MVC3 application that uses Windows authentication and works great if we deploy it on a server that is in the same domain with the users that access it.
I have a request to deploy the application on a external server, like Amazon, and use ADFS to authenticate users with their domain credentials.
Does anyone have some tutorials how to implement this functionality into a MVC3 application? I didn't find any resources to help me with this issue.
The core technology you need to look at is WIF (Windows Identity Foundation). The WIF SDK has plenty of examples of use, and I would start there.
This exact scenario is described in detail in this chapter:
http://msdn.microsoft.com/en-us/library/ff359102.aspx
I would suggest you should start with the intro sections of the same guide to understand how "claims based identity" works and the components involved.
For ADFS, I would suggest Lab 1 of this:
http://claimsid.codeplex.com/releases/view/68061
I need to integrate shibboleth in my application. My application is .net web application. May I know how to do this one? I have a separate server (ubuntu server) in which shibboleth idp and sp installed with apache configuration.
I made lot of search on this. but I can't able to get the correct information for this one Can anyone suggest me some url or point what i need do to get it work?
You could implement (Windows Identity Foundation) WIF in your ASP.NET Web App.
If you have Active Directory Federation Services (which basically make Active Directory speak SAML2 protocol and WS-Federation protocol), you can have ASP.NET with WIF trusting (thru WS-Federation) ADFS V2, trusting (thru SAML 2 protocol) Shibboleth.
You can find additional information in these posts. You can find sample screen shots with SharePoint instead of ASP.NET in this post (sorry it's in French). A white paper explains how to implement.
If you don't have Active Directory and ADFS V2, you may want to use SAML2 protocol extension for WIF and this thread may help.
Similar to : Single Sign on using Shibboleth