Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

- Employ Atlassian Crowd as the administration console for user authentication.

Open Questions

...

 - What's the cumulative file size on the Sage SSH server?

...

- if we are doing "arm's length" integration with google app's, then what other providers should we plan for? - do we need 'audit logs', e.g. to show when users were added/removed and by whom?

Experiment to address key questions

...

- Set-up Crowd trial edition (where would it run?)
- Change Google Apps demo domain to authenticate against Crowd
- Change/deploy GAE app, authenticating via Google Apps
- Add user to Crowd
-Try to access Google Apps via this user (e.g. make a document)
- Try to log into to GAE app via this user
 (If not, can GAE OpenID option work with Crowd or can bypass UserService to use some sort of OpenID connector to reach Crowd?)
- Try to add user to a group in Google Apps
 (If not, then can use gmail OR can use Provisioning API to create account?)

Experiment execution

...

1. Added - Added 140.107.149.214 deflaux to C:/etc/hosts on my lap top.  I can now PuTTY/SSH into 'deflaux' which is a Linux box in Nicole's office.

2. Followed - Followed http://confluence.atlassian.com/display/CROWD/Installing+Crowd+and+CrowdID2.1 downloaded zip file

- downloaded zip file

- downloaded and installed WinSCP; connected to deflaux:22 using SCP protocol.

- unzipped zip file and copied contents to /home/hoff on deflaux

Notes:

Google Apps provides two APIs to help with authentication:

...