- Constant Contact Community
- :
- Developer Community
- :
- Authentication and Access (ie. 401 errors!)
- :
- API Key for multi-user, multi-site application
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
API Key for multi-user , multi-site applicatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-15-2012 10:24 AM
I want to get an API key from my account and tie it to a wordpress plugin which can then be installed on any wordpress website.
The API key requires a redirectURI -- this URI is custom for every wordpress install:
http://mySite.com/wordpress/wp-content/plugins/mai
http://yourSite.com/wp-content/plugins/mailsign/ct
while I could generate that url and walk my users through generating their own API key with a custom redirect URL specific to their website, this is a _mess_. I am confident that any instruction I could provide will at best be a hassle and at worst confuse all but technically savvy users.
I desire to make my plugin usable by novice users looking to add constant contact support to their website.
How can I setup a cross-domain API key without the need for custom-tailored redirect URIs?
Re: API Key for multi-user , multi-site applicatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-15-2012 10:30 AM
Looks like three-legged authentication is the answer as opposed to OAuth 2.0 through the CtCt wrapper
I'll post again if I have more questions or find out something interesting :)
Re: API Key for multi-user , multi-site applicatio n
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-16-2012 01:40 PM
Hey Chad,
Definitely let us know if you have questions. I've been working through some OAuth2 scenarios as well, and three-legged authentication does seem to be the best way to handle"novice-proofing" your OAuth2 authentication.
Support Engineer


