LDS Connect Version 2.0 (developer preview)

6 views
Skip to first unread message

AJ ONeal (Home)

unread,
Mar 20, 2015, 10:47:59 PM3/20/15
to lds-c...@googlegroups.com, John Potter, Bennington Branch Executive Secretary, oh.wi...@gmail.com
LDS Connect v2:

(This is a developer preview. The site will go live on ldsconnect.org in a week or two)

Working Zero-Config Demo:
https://github.com/LDSorg/frontend-oauth2-browser-angular-seed-example

Major Features
* Browser-Side (Implicit Grant) OAuth2
* Persistent Access Tokens
* Users can link Facebook to their LDS Account (Google+ forthcoming)

NOTE: I will be updating the privacy policy.
* User data will only be sent to the browser.
* You MUST NOT pull user data (pictures, emails, phone numbers, etc) to your server.
* I will be providing tokens for users, phone numbers, and email addresses
  (You may use these tokens to interact with users through ldsconnect.org)

With this change the apps you create will no longer be in violation of the church's privacy policy.

Also, I've shared my work with a few church employees and they were blown away. I'm finally setting up a meeting with one of the big dogs at the Riverton Office building.

Progress. :-D

AJ ONeal

AJ ONeal (Home)

unread,
Mar 20, 2015, 10:55:31 PM3/20/15
to lds-c...@googlegroups.com, John Potter, Bennington Branch Executive Secretary, oh.wi...@gmail.com
Major Features
* Browser-Side (Implicit Grant) OAuth2
* Persistent Access Tokens
* Users can link Facebook to their LDS Account (Google+ forthcoming)

Also, I'm switching over to using a different set of APIs so it will be *MUCH* faster overall.
Also, the architecture is nearly PCI compliant
* Asset Server is public facing
* API Server is private and proxied (the proxy is a little slow, I'll figure that out later) (encryption forthcoming)
* Session Server is private, proxied, and encrypted
* Key Server is private and only connected during reboots.

AJ ONeal

John Potter

unread,
Mar 20, 2015, 10:57:50 PM3/20/15
to AJ ONeal, oh.wi...@gmail.com, Bennington Branch Executive Secretary, lds-c...@googlegroups.com

Can my server still store the lds internal id?

AJ ONeal (Home)

unread,
Mar 20, 2015, 11:05:14 PM3/20/15
to John Potter, oh.wi...@gmail.com, Bennington Branch Executive Secretary, lds-c...@googlegroups.com
I'm going to give you an app-scoped-id, but I don't export that yet, so I'm still providing the lds account individual id at the moment.

Can my server still store the lds internal id?

AJ ONeal (Home)

unread,
Mar 21, 2015, 2:57:39 AM3/21/15
to lds-c...@googlegroups.com, John Potter, Bennington Branch Executive Secretary, Cory Brown
Also, the frontend is completely and entirely decoupled from the API such that you can run your own local copy with a single command:





The local copy will run against the real API server. One day - hopefully weeks, not years - I'll have dummy user accounts (plural!) so that you could work on the interface in various conditions - such as an unverified account, a partially verified account, etc.

My design skills are limited, so I welcome any help with this.

AJ ONeal

AJ ONeal (Home)

unread,
Mar 26, 2015, 7:29:10 PM3/26/15
to lds-c...@googlegroups.com, John Potter, Cory Brown, Trevor Allred, Peter Pavlovich, Randy Secrist
Lot's of good updates on https://lds.io

* login and view your ward data from the hope page
* register, update, and delete apps
* some documentation is up

I've updated several of the examples:

https://github.com/LDSorg/frontend-oauth2-browser-jquery-example

Since I haven't heard from anyone saying that they're still depending on ldsconnect.org in production, I'll probably replace the site tonight or tomorrow.

AJ ONeal


On Fri, Mar 20, 2015 at 8:47 PM, AJ ONeal (Home) <cool...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages