| Welcome to LawsonTalk. We hope you enjoy your visit. You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it. Join our community! If you're already a member please log in to your account to access all of our features: |
| What is the *POINT* of RM? | |
|---|---|
| Topic Started: Jul 19 2009, 06:13 AM (739 Views) | |
| hremail11 | Jul 19 2009, 06:13 AM Post #1 |
|
Member
![]() ![]() ![]() ![]()
|
I understand Resource Manager and LDAP, so my question isn't WHAT IS RM. My question is: What is the *POINT* of RM, or at least of RM being in LDAP? So far, my experience is that Lawson is using a custom schema to put RM into MS ADAM. And, user entries (and passwords) are all stored in Lawson's own format. So that means I can't use any standard AD/ADAM tools to manage users, change passwords, suspend users, change roles, etc. To me, that means that Lawson/ADAM is just another database. I don't get any of the advantages of a standardized LDAP implementation. I can't use any of my previous tools. I can't use my existing knowledge of how to enable/disable users. And so on.. So can someone explain to me the advantage of RM being in LDAP? It's almost like Lawson chose LDAP to check off "uses that new fangled LDAP" on their checklist, but otherwise.. that's it. No other point. Thoughts? |
![]() |
|
| arvin | Jul 20 2009, 01:28 PM Post #2 |
|
arvinojales
![]() ![]() ![]() ![]() ![]()
|
I would say Single Sign On is one of the main reason why Lawson uses LDAP. Arvin Ojales |
![]() |
|
| schroncd | Jul 21 2009, 06:49 AM Post #3 |
|
Lawson Technorati
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
I think Lawson really wanted to give you the opportunity to bind to your corporate password repository, which LDAP enables. Secondarily, they had to put security in something other than GEN because you have to HAVE security access to read GEN data. Maybe a SEC database in your RDBMS would work, but how would you control the security for it? And nothing is a fast to read as LDAP. We all know what putting GEN in the RDBMS has done for compile times. Could you imagine what it would be like to get security clearance for everything a user does from a similar system? Performance is the reason Lawson kept GEN as an ISAM structure for so long. As for why Lawson modified the schema, it was probably specifically to foil existing LDAP tools. You don't really WANT any Joe who can download them to be able to manipulate your security structure. Disclaimer: these are my thoughts only. I have no internal knowledge of Lawson's reasoning on these matters.. |
![]() |
|
| trezaei | Oct 2 2009, 07:12 PM Post #4 |
|
LawsonTalk Addict!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Those are actually the best reasons I've heard so far for this Dave. Especially the custom schema which bugs the heck out of me. |
![]() |
|
| « Previous Topic · LSF 9.0 · Next Topic » |





![]](http://z5.ifrm.com/static/1/pip_r.png)



12:35 AM May 19