We have a a custom membership provider with InfusionSoftProvider in our web.config which is used to validate keap contact users upon authentication in our third party .netv4 application.
Question is will this no longer work after the legacy key sunset as of today 31/10/2024?
Pav
(Pav)
October 31, 2024, 5:39pm
2
Welcome @Filimoni_Naisua_5939 ,
Microsoft .NET v4.0 was initially released in 2010, which indicates to me that your integration is using the Legacy API Key.
Have you contacted your membership provider in providing you an update to their software?
Is your provider still around?
Keap have not said anything today about the blackout at the moment.
1 Like
yes Iām the working on the update, we recently took over the migration codebase and I needed some confirmation on this. thank you!
Pav
(Pav)
October 31, 2024, 8:51pm
4
It should not take you long to make the changes, although it depends on the language and the complexity of things.
Keap Legacy API Key Migration documentation does have a C# example that will help.
https://developer.infusionsoft.com/legacy-key-migration/
Just make sure you change the API Endpoint URL and provide the Service Account Key via the Request Header.
1 Like