Subject: Grouper Users - Open Discussion List
- From: Chris Hyzer <>
- To: Peter Schober <>, "" <>
- Subject: RE: [grouper-users] new to grouper (again)
- Date: Thu, 22 Dec 2011 20:02:20 +0000
- Accept-language: en-US
> From the QS Linux install (ant ui): "type default and press enter".
> What kind of default is this when it defaults to "exit" and you
> literally need to type "default"? Very minor blemish and might be some
> ant thing, of course.
At some point our build scripts will be maven, which will fix this
> I haven't yet figured out where to unpack and build stuff vs. where
> the software and it's data are installed. I had to fight a bit with
> logs not ending up where I would want them, and having the wrong
> permissions (since they seemingly needed to be written to by the user
> running the stuff on the console, as well as the user the container
> runs as; both non-root in my case). I moved logs and software
> directories where I wanted them and left a myriad of symlinks where
> there where, for now (so I wouldn not have to change all those
> properties files with "../grouper" references etc. I did set up
> grouper.home property in my containers environment). I'll look into
> this later, once I learn more about involved files.
Im working on a proof of concept on an easier quick start which would help
address some of this stuff...
> Beyond that I haven't done much yet except explore the UIs:
> Simple things like browsing though the groups and trying to add a
> member where confusing at first: I saw that there was an "Ian Windsor"
> in some group, so I tried to add this user to another group (Admin UI).
> But searching for "Ian" or typing "Ia" in the LiteUI (for
> auto-completion) didn't bring up any results -- only when written in
> lower-case ("ian", "ia") results where found. Even though the results
> themselfs were presented in initcaps ("Peter Bush", "Ian ...").
That's weird, I opened a bug:
> When in the Lite UI I always seem to want to click on folders to
> browse the hierarchy but these are not clickable. They are in the
> Admin UI, though.
Right, the light UI is supposed to be more "sandboxed" where you cant do
other things except edit the direct members of one group
> When I select a group in "Create or edit groups and roles" (Lite UI)
> and then "edit group/role", and then "memberships" at the bottom, I
> lose the standard header with the Internet2 and Grouper logos,
> including a link to the "Main Menu". It's all there one click before
> that. Looking closely there's "Admin UI" and "Lite UI menu" written in
> tiny letters right to the name of the group (in the line "Current
> location is"). But I wonder why logos, logout link, etc. all vanish
> on that specific level. Using the browsers back button the group I
> selected before is of course gone and I'm back to searching for it
> again. Making the group itself (in the line "Current location is")
> clickable (in the "Group membership update lite" page) would make this
> unnecessary, I would hope.
Right, it goes to the lite UI membership screen
> After searching for a group (LiteUI) and selecting "Privileges"
> instead of "Memberships", the current page becomes longer and gets a
> "Group / role privileges" section. The rest of the page remains the
> same ("Main menu", "logout" links, logos are intact).
> When selecting "Memberships" the current page is replaced with a new
> one, and the header is gone. Probably this is because there might be
> many members being shown there (which is not the case in the QS, of
> course), but then having the page header there for consistency won't
> make things much worse?
The UI will be rewritten in 2.1
> I followed "Grouper Getting Started Quickly" setting up non-QS
> Grouper (RHEL6, Java6, Tomcat7 and with the Oracle RDBMS) until I had
> the grouper client fail to connect to WS (with a HTTP 403 from
> Tomcat), but I'll keep those questions for another thread if the error
> persists. I'll need to pick this up sometime after the holidays.
> Of course I also have non-technical questions about naming plans etc.
If the WS are running successfully, then the WS URL in the client config
could be off, or the authn could be off (config on client or server)...
- [grouper-users] new to grouper (again), Peter Schober, 12/22/2011
Archive powered by MHonArc 2.6.16.