Wordpress FB plugin - authentication

I am currently trying to make use of a FB login plugin for Wordpress.
In one of the support threads, it mentions the issue I am having is commonly fixed if you:
“Switch the “Encrypted Access Token” setting to ‘Enabled’.”
I don't have this option in the advanced app settings:
http://dl.dropbox.com/u/35816363/otto.jpg
Can someone please advise what is wrong in my app settings that this option is not available?
Thanks
Lee

Have you migrated your app to oAuth 2.0? As far as I know, that setting “Switch the “Encrypted Access Token” setting to ‘Enabled’.” will only appear when you've set your app to oAuth 2.0.
I think you could accept the migration by activating the Open Graph feature in the app settings [-> get started] (if not, I apologize in advance; I did this many moons ago ^^;) On a side note: Activating Open Graph comes with the Timeline preview in your FB profile.

Related

C++Builder TWebBrowser doesn't work with Google OAuth login

I maintain an application written in C++Builder 2009. Part of it involves using a TWebBrowser control (based on Internet Explorer) to send users to a Google login page in order to obtain an OAuth key. This has worked well for a while, but now Google, bless their hearts, has implemented some kind of security upgrade, and now my users get to a page that says "Couldn't sign you in, this browser or app may not be secure". FYI, I am already setting a Registry key that is supposed to make IE run in version 11 emulation mode.
I do have a couple of workarounds: If the user runs IE first in admin mode, signs on, leaves it up while running my application, we don't get the problem. Second, I can start up the default browser - Chrome, IE, whatever - and send them to the URL for OAuth, then it avoids the error message.
The problem with this solution is that without being able to hook into TWebBrowser events, I don't have any way to automatically retrieve the OAuth key - it is necessary for the user to cut/paste it into my application. I'd like to avoid these clunky solutions.
I should also mention, this problem occurs only for certain Gmail accounts. I have no idea what the difference is between accounts that work and don't work. Any ideas on that?
So, is there any way to configure IE or TWebBrowser so this security issue is bypassed? Or, if I was to update to a modern version of C++Builder and use TWebBrowser (or something else?), would this problem be avoided? Any other ideas to fix this problem?
The latest C++Builder supports Google's Chromium engine, it's probably safe to say it'll be compatible with Google's security upgrades.
Powerful Chromium Based WebView Component To Host Web Content In Your Delphi/C++ Builder FireMonkey Apps

Google Identity API / GitKit - change domain on a production app

We are using GitKit API in production projects - and there is an urgent need to change the domain of one of our existing projects.
This is normally done under Google Cloud Console - in API Manager under "Identity Toolkit API" -> "Edit" link. Unfortunately, this link is gone - it was probably removed this week?!
We know the new projects should use Firebase Authentication (as announced on Google I/O this year) and we have started to work on upgrading our auth code and we are keen on using it in new projects.
But our existing production projects cannot be migrated easily!
We have not been alerted anyhow in advance, that "Edit" on existing projects will be disabled - and there is no deprecation date specified at https://developers.google.com/identity/toolkit/migrate-firebase or in the alert messages. As paying Google Apps customers we rely on many Google products. This is a very unpleasant surprise.
Is there any way how to restore the "Edit" for "Identity Toolkit API" for existing projects? As I said, we urgently need to adjust a domain of an existing production project. Any help from the Google engineers would be greatly appreciated.
Sorry for the inconvenience. We have rolled out the fix, and the Identity Toolkit API setting page should work now.

How to use Single Sign On in a Vaadin application

I have a Vaadin 7 application that needs to use SSO (or a better kind of enterprise sign on method?) to authorize users through an LDAP directory. I also need to use groups or "roles" to differ between users and what they are allowed to access in my application. I am new to both login processes and Vaadin, and all I have right now is a working login form in my application that authorizes users against a fake "AD class" that I made myself.
So...
Where and how do I even start?
I read something about portlets and Liferay in this context. Is it even possible to achieve my goals without using Liferay or portlets?
Are there any good Vaadin addons that can help me with this? 
Can I use Spring security for this? (I am using xpoft SpringVaadinIntegration addon and I know it handles roles for example)...
If I sound lost, it's probably because I am. I will gladly read up on this, if I even knew where to start. Please help me chop this monolithic blob of confusion into smaller pieces =)
 
SSO with windows login only works in the intranet and it requires the use of kerberos or ntlm.
You can use a library like waffle to integrate things.
Look here:
Link #1
Link #2

joomla 2.5, user authentication

I am currently trying to work out a solution, how to make an authentication for my Joomla 2.5 website.
I did the log in form, and created test users, although I don't know how to access Joomla DB. Can you help me find a solution for my question. The answers I found on google, I didn't quite understand.
It would be really nice if someone would share some good tutorials.
Thank you in advance.
Joomla manages authentication for you via its user management and authentication system. It already provides you with a login form in fact ... but more importantly it provides you with authentication and user plugins that you can add your own to if you need something different. This is the point of using a CMS to have a platform that already provides you with secure and well tested user management among other thigns.
Try this , I think it will be useful to you,
http://docs.joomla.org/J2.5:Accessing_the_database_using_JDatabase

Adding a Sandboxed app to Login Items

I have read through many questions here about launching my app on login. I have followed this awesome tutorial suggested many times. That tutorial does work. BUT...
The one side affect that comes from using a helper app and registering it using SMLoginItemSetEnabled is that my app does not show up inside the user's Login Items in System Preferences.
There are several apps in the App Store (such as PopClip and Dash) that do what I am trying to do. I just can't figure out how...
UPDATE: I found out from the Dash developer that Dash is actually not sandboxed. He also believes that PopClip is not either. This could explain things... https://alpha.app.net/kapeli/post/3975968
UPDATE #2: I just got confirmation from the PopClip dev that it indeed is not sandboxed as well. https://twitter.com/pilotmoon/status/313746294361427968
With the last 2 updates, I guess the answer is clear. As of today, there is no way to accomplish this with Sandboxed apps.
Hope it's not too late.
In Apple's "Daemons and Services Programming Guide":
Adding Login Items
There are two ways to add a login item: using the Service Management framework, and using a shared file list.
Login items installed using the Service Management framework are not visible in System Preferences and can only be removed by the application that installed them.
Login items installed using a shared file list are visible in System Preferences; users have direct control over them. If you use this API, your login item can be disabled by the user, so any other application that communicates with it it should have reasonable fallback behavior in case the login item is disabled.
In sandboxed environment, only Helper applications can be installed in login items. You need to create one, stored in the Contents/Library/LoginItems folder of the main application.
Then you can used SMLoginItemSetEnabled to set the helper as login item and ask the login item to start the main application.