I am getting error "CWWIM4538E Multiple principals were found" at server startup. I know the cause as the local WAS admin account has its duplicate in LDAP repository. I simply wants to remove the local WAS user gracefully offline as server won't come up. I tried playing around with changing the user id info in fileregistry.xml and corresponding change in security.xml but to no avail.
Seems that you've added LDAP into "federated repositories" and forgot to remove "internalFileRepository" which contains wasadmin as well. You can do it in profiles/dmgr/config/cells/myCell/wim/config/wimconfig.xml, where you just remove it from the realm.
Related
I have a simple etcd server running and I am using this github project called etcd-keeper to visualize the data in the etcd.
you can find the etcd-keeper project here: https://github.com/evildecay/etcdkeeper
I have created the root using etcdctl and everything works fine.
And I needed to create a another user that has limited view access. So, I created another test-user user and added read-only role with relevant persmissions.
Everything is good but, when I try to access the etcd server using etcd-keeper it doesn't allow me to log in with the test-user credentials unless I signed in with root user first
I don't need to share the root user credentials with the person logs with test-user. Otherwise no point in creating a new user noh.
I get this warning as below:
Can someone please help me to fix this problem? Is this error from etcd servr side? Anyone has used this etcd-keeper before?
Thank you.
I'm working on a tool that generates .rdp files and then invokes them using Microsoft RDP Client. This tool is running on Mac OS.
Everything works well, the only problem is that I can't figure out of how I can generate 'password 51:b' field properly. On Windows this can be done easily by using CryptProtectData method from Crypt32.dll library. How can I do the same on Mac.
Another option could be to use "rdp://" URL scheme, but it doesn't seem allow to pass password this way.
So the question is how can I implement auto-login on Mac if I use third-party RDP client.
As far as i know you can't. You can however create a "User Account" and a Server configuration and add both to the client. The connection will then be visible on the main window and you just need to double click it.
To do so, you need to add the password to the Keychain, use /usr/bin/security to do so from a script. It needs to be a generic-password and saved in com.microsoft.rdc.macos. Also be sure to generate an ID according to the RDP Clients scheme, like BFF77777-7777-7777-7777-777777777777.
You may also set the permissions to read that key using /usr/bin/security and set-generic-password-partition-list specifying the right teamid (UBF8T346G9) and again com.microsoft.rdc.macos. You need the admin password to do this step.
Then you can alter the RDP Clients config file, which is a .sqlite file located at /Users/$(whoami)/Library/Containers/com.microsoft.rdc.macos/Data/Library/Application Support/com.microsoft.rdc.macos/com.microsoft.rdc.application-data.sqlite. Add the user configuration in the ZCREDENTIALENTITY table and make sure the ZID matches the one added to the keychain.
To add a server configuration you need to alter the ZBOOKMARKENTITY table. Just add a configuration by hand using the UI and look at the table to get a feeling of how it needs to be setup. Basically you link your user configuration with the server configuratio by making sure that ZCREDENTIAL in ZBOOKMARKENTITY matches Z_PK in ZCREDENTIALENTITY of your user configuration.
I know the answer is a bit late, but it may give you a starting point. This will however not fully automate the process, you will still need to go to the UI and double click the connection you want to use.
I have DB2 11.1 installed on Windows 7. 'db2admin' user account was created to access this. I was able to create, select and perform all necessary actions. Everything was working properly, until one fine morning it started giving me this error while connecting to database.
SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001
I performed below things:
Reset the password
Verified if the user account is disabled on Windows.
Account is not disbaled
Verified if the account is part of appropriate groups and ensured it has all necessary privileges on Windows
User groups
Deleted the 'db2admin' account and created a new one.
None of them worked and am still unable to figure out the reason for this error.
Is the error misleading? If so, any suggestions to verify logs or anything to figure out the root cause?
Any help in resolving this is highly appreciated
I am trying to create a liberty cluster. While generating the keys, liberty is creating some keys under logged-in user's home directory which is c:\users\xyz\ .ssh.
How do I say liberty to save the keys under d:\users\xyz\ .ssh?
I need this because, i am working in citrix environment and c drive image is always replaced upon restart and I am loosing the keys forcing me to create the cluster again or save a copy of the keys before I log out for day.
Did you try displaying options for registerHost action like this:
D:\Liberty\wlp\bin>collective.bat help registerHost
it shows rpcUserHome param, which might be what you are looking for:
--rpcUserHome=path
Optional. The home directory for the user with which to authenticate
to the RPC mechanism. Defaults to the current OS user home directory.
This value is used when generating SSH keys.
I created a user in weblogic by following the below steps:
1. clicked on security realams present on left side panel.
2. clicked on myrealam
3. clicked on user and groups
4. clicked on new
5. Provided user name and password
The user created successfully. However when I am starting the server by deleting the log,cache, tmp and data folder. The created user is getting deleted automatically.
From my first level analysis I found its due to the deletion of data folder.
I want to create a permanent user for security validation.
Can anyone Please help me to create a permanent user.
Regards
Asutosh Kar
I got the answer to solve my above issues.
There are 2 ways to solve the above issue:
1. Export the LDAP files from the security realms to a directory present in the server and delete the data directory and restart the server. After restart of the server again import the LDAP files.
2. Modify the DefaultAuthenticatorInit.ldift present under the domain security directory to add the user and group details. After that delete the data directory and restart the server.
Regards
Asutosh Kar
I tried following and it works
Login to weblogic console.
Navigate to domain.
Under domain , security tab > Embedded LDAP
Select Master First and then restart servers.
The users created after restart will remain in the system