substitue SSOP id while using AD BIND

 6 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Ashley Ardoin
New Member
Posts: 3
New Member

    Need to be able to substite an SSOP identity ... Example have an RMId of pr100rw1, a SSOP User of jsmith (bound to AD), and OS id (Window NT) of localcomputer\xpr100rw1 (local computer account...not AD account!)... would like to change out SSOP User jsmith (AD account) with mjane (also an AD account)  and leave the rest unchanged... an thoughts

    John Henley
    Posts: 3353
      This should be easy...delete the SSOP identity [jsmith] for that RMID [pr100rw1], and add the new one [mjane].
      Thanks for using the LawsonGuru.com forums!
      John
      Ashley Ardoin
      New Member
      Posts: 3
      New Member
        forgot to mention that I don't want to use Lawson Security Administrator but rather some custom created program or even something like loaduser
        trueblueg8tor
        Advanced Member
        Posts: 41
        Advanced Member
          I believe you can accomplish this by creating an xml file and using it with ssoconfig. There should be directions in either the KB or the Security administration guide.
          Ashley Ardoin
          New Member
          Posts: 3
          New Member

            Thanks, we got it to work by using the loaduser xml. Our biggest problem was getting lawson to reread the security setting and not use cache without doing a stop lawsec and then restart.

            John Henley
            Posts: 3353

              "Our biggest problem was getting lawson to reread the security setting and not use cache without doing a stop lawsec and then restart. "

              How did you accomplish that?

               

              Thanks for using the LawsonGuru.com forums!
              John
              RMS
              New Member
              Posts: 2
              New Member

                I 've been working on this for Ashley.. We're not sure why it's working now.  A year ago we were having that caching problem.  Now, having applied a year's worth of patches, the problem went away.  I suspect one of the patches broke something, resulting in our being able to use loadusers to manage SSOPs.  No doubt, after some future patch, we will be SOL again just as inexplicably.