Hi,
I finish first working proof of concept of roles management. Please try it and write what do you thing about it.
You can test it directly from git as it is still under heavy development. Just run rake deploy_local for (for webservice-base and webservice-roles).
description:
each role contain permissions and users. Permissions say what permission has user involved in role. Permissions is unioned so if you have role RBA which has time.read and role RB time.write, then user which is involved in both roles has rights to time.read and time.write
known issues:
- User interface is still far from my idea. it should be accordeon which open role with two tabs for assign user and permission
- you can do suicide if you remove assign user which runs webyast to roles which doesn't have permission.write
- user is only one which is known to Users module
Feel free to write your opinions, ideas and complains (and of course bug report as it is really just non-stable preview)
Josef
--
Josef Reidinger
YaST team
maintainer of perl-Bootloader, YaST2-Repair, parts of webyast
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
John,
once again, could you please sent replies to the mailing list instead of
replying to me directly. Others might be struggling with similar problems
as you.
Am Dienstag 25 Mai 2010, 17:53:33 schrieb Developer Coldfusion developer:
> LDIF file is in attachment. Also I had to configure OpenDS to make it
> use pre-encoded passwords
> http://blogs.sun.com/Ludo/entry/opends_tips_importing_ldif_with. John
The schema you attached looked good to me on a quick view (at least it
had the required inheritance between the suseObjectTemplate and
suseGroupTemplate Objectclasses.
Honestly, if you really added the attached scheme I think you probably
hit a bug in the OpenDS Version you are using and not in YaST. What YaST
ldap-client tries to add this object to the LDAP Server:
dn: cn=grouptemplate,ou=People,dc=linux-1xek
cn: grouptemplate
objectClass: top
objectClass: suseObjectTemplate
objectClass: suseGroupTemplate
suseNamingAttribute: cn
susePlugin: UsersPluginLDAPAll
Your OpenDS seems to choke on the fact that the objectclasses
"suseObjectTemplate" and "suseGroupTemplate" are present in the entry.
Which both are defined as being "structural". Usually (if
suseGroupTemplate would not inherit from suseObjectTemplate), OpenDS
would be correct with it's complain. The LDAP standard allows an entry
only belong to "precisely one structural object class superclass chain"
(see RFC4512 for details if interested). But as suseGroupTemplate is a
subclass of suseObjectTemplate this constraint is fullfilled. And that's
why I think you hit a in OpenDS.
Unfortuntely I don't have an OpenDS instance running here to test that
myself. But I'd suggest you create bugreport with the OpenDS people. Make
sure you test with the latest release, probably this has already been
fixed.
[..]
--
Ralf
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi. I still have "...violates the Directory Server schema
configuration because it includes multiple conflicting structural
objectclasses suseObjectTemplate and suseGroupTemplate" bug. Attaching
a log. Please help someone. I am stuck! John
kkaempf, vgorobets, schubi, mzugec, jsuchome, mvidner, jreidinger
Status:
- final validation testing on all architectures revealed no more
ship-stoppers
- critical bugfixes will go out as maintenance updates.
- this means WebYaST is *gold*
(WebYaST-Pool is frozen, updates go to WebYaST-Updates)
- git trunk is open for development again
next stop: WebYaST 1.1 for ATK 1.1
Outstanding action items:
- Help documentation team ! Actively approach Jakub and offer help.
- Fix critical/major bugs, follow the maintenance process
- Fix other bugs in trunk
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
kkaempf, vgorobets, jsrain, mzugec, schubi, jsuchome
absent: mkudlvasr, jreidinger
This week: SP1 GM
Help documentation team ! Actively approach Jakub and offer help.
vgorobets:
- no update
next:
- test GMC
jsrain:
- no update
next:
- brainshare
schubi:
- worked on Selenium, looks complicated
next:
- more Selenium learning
mzugec:
- non WY
next:
- non WY
jsuchome:
- non WY
next:
- non WY
- learning
kkaempf:
- testing and bugfixing on big endian architectures
next:
- clarify work for ATK 1.1
- more big endian testing
jreidinger:
- testing
next:
- focus on remaining features (roles mgmt)
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi,
I recently finished reading of pro-GIT book and I found there few usefull commands ( maybe common command with interesting option).
usefull commands:
git add --patch (see man) - more universal git add -i
git diff --check
git log <branch2> --not <branch> better one is git log <branch>..<branch2>
git log --left-right <branch>...<branch2>
git rebase -i <rev>
git blame -C
git submodule
file .gitattributes and e.g. filters
git fsck --full
I also found link to site where is specified how should goot commit message look so all options e.g. for log work as expected. http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
--
Josef Reidinger
YaST team
maintainer of perl-Bootloader, YaST2-Repair, parts of webyast
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
