Hi everyone, I have a user who recently changed her company userid, which is the account info we use for our WF userids. Is there an easy way to change this in Ver.7.7.03 (we'll be upgrading to 8.2 soon) so that she doesn't lose any of her existing reports or accesses which are under the old userid? For instance her old id was abc123 and her new id is def456. All of her info needs to be available under def456. Thanks in advance!

This message has been edited. Last edited by: FP Mod Chuck,

PhillyPat

Are you using Internal or External authentication in the MR Security Settings from the Administration console?

Hi Chuck,

First, I apologize for taking so long to respond. Juggling too many projects these days (aren't we all)? Also, I didn't have Notifications set to On (I do now!)

When I go into the Admin console and look at the MR Security settings, I see the following:

"REPOSITORY_DRIVER set to MR Realm Driver"

For Authentication, "Trusted" with "Use Webserver REMOTE_USER variable" also selected.

For Authorization, "Internal" is selected.

Any help you can give me would be greatly appreciated!

Thanks,
Pat

Under 7.7.03 "moving" a user id to another one it's a manual process that is not simple and where it's easy to corrupt the whole setting.
So you need to have backup of all original files and folders.
I also do suggest to try it first under a test/dev environment.

If I do remember properly here are the steps:

1- Create your new user id from Managed Reporting Administration
2- Stop Tomcat & WebFOCUS services
3- From a Windows explorer go to : .../WebFOCUS77/basedir
4- Locate the folder with the new user id and make a copy : def456
5- Locate the htm file with the new user id and make a copy : def456.htm
6- Locate the file user.htm and make a copy
7- Copy old folder abc123 over def456
8- Copy old file abc123.htm over def456.htm
9- Edit the new def456.htm and change all reference to abc123 by def456
10- Edit file user.htm and change all reference to abc123 by def456
11- Start Tomcat & WebFOCUS services

The old abc123 should not be affected and still work. Once you are sure that the new def456 work properly you can then remove abc123 using Managed Reporting Administration

GL

Thanks Martin, I'll give this a try.

Pat