Skip to Content.
Sympa Menu

comanage-dev - [comanage-dev] Notes: Dev Call Friday (26-Dec-2014)

Subject: COmanage Developers List

List archive

[comanage-dev] Notes: Dev Call Friday (26-Dec-2014)


Chronological Thread 
  • From: Heather Flanagan <>
  • To:
  • Subject: [comanage-dev] Notes: Dev Call Friday (26-Dec-2014)
  • Date: Fri, 26 Dec 2014 10:40:21 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/25/14 8:29 AM, Benn Oshrin wrote:
> For anybody who is around, let's go ahead with the dev call
> tomorrow. If nothing else, we can use the time to discuss the new
> demo VM. Other agenda items according to who shows up.
>
> Merry Xmas (pronounced as it's written),
>
> -Benn-

1. Demo
Moving to new production SCG IdP. We will use the SCG Google account.
The IdP will have an extra button when we're trying to get to the
registry pointing to Google, and we'll authenticate with that, go
through an enrollment flow, and from there set an OpenLDAP password,
using that going forward when using the SCG IdP. Scott will send
instructions.

Could we use the Google bridge for the SPs on the new demo
infrastructure so people could authN before we're in the InC metadata?
Maybe, but would require some coding and it's fairly low priority.

List of CO's that's currently defined on the demo server: can we clean
that up?
We can clean up the UT one, as well as the two LIGO one.

2. Default enrollment
Suggest: Invitation-based enrollment, Self-sign-up enrollment,
Administrative enrollment
Best to have self-signup enrollment to have as few text fields as
possible, as opposed to separate org and CO person boxes.
Account linking should also be included.
Additional role enrollment will be a good thing, but it doesn't work
right now.

Already in JIRA: see CO 273


3. 0.9.2 tagging
Haven't tagged in a while; should do that.
What have we done since 0.9.1: normalizations, additional extended
types, and expirations
Not sure it's worth committing right before new year, since we are
also sending out an announcement (no one will read it). Team should
use this week to finalize the 0.9.2, then it will be committed around
the end of next week.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUnauVAAoJEBTitMubYA+Rb5IH/3aNtQjHDMvGhb4qZYiDDbZs
tFU31mxQmHheMBjklvyZfWR44bGqpCoAHOMq6q2XvGrkqhbjnIcTZ5eS7tVUT3/f
Au8wM0Y6dWTloNFh8XA1CP1p0+lfA1UY+QABmCQoX+IPG3HHU8ON44bqg0P0E1Ek
DKu980joX3jbpbRZPs48n5WcSVK75VMXbvyJtQtxOQFp+sVsHnJXfJCRsk5QHBYq
IhmPgM6MXhn16XsG0PoRiSE9mPbWbk15HwHPunq5xI7FtwZXXHrdIRjsNWEqyPHn
Vfr9LtKVYuNDNe8RWHFB5vSYTKXKwhqbfdrCwi0Qka1e3Y6xwhEamd5mgbeKsbI=
=qjKY
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.16.

Top of Page