Skip to main content

How to re-certify Lotus Notes ID Manually?


If you see above alert box, understand that you need to re-certify the user’s lotus notes ID.
First export the user’s lotus notes ID as “SAFE.IDS” or get the expired  user’s lotus notes ID and save it on Removable Storage Drive or Shared Network Drive that can access from Domino Server.
Then log in to Domino Server and click Configuration Tab, Expand Certification and select Certify as shown below.
After that Click Certifier ID and choose cert.ID.

Type correct password for Certification ID and click OK.
Then Choose the SAFE.IDS or Expired User’s lotus notes ID that you saved at first step.
Type the current user’s lotus notes password and click log in.
Click Certify if you see prompt windows as shown below.
Click NO if you see prompt windows as shown below.
User ID re-certify task done from Domino Server Side.
Go to user’s PC/Notebook, open lotus notes and Click File>Security>User Security
Then you will see prompt windows that ask you to key in the password.
Key in the current user’s lotus notes password.
Expand Your Identity, Select Your Certificates and Click Get Certificates.
Then Select Import (Merge) Notes Certificates and choose the Re-certified ID from your Removable Storage Drive or Shared Network Drive.
Key in the password if prompt.
You’ve done the task of lotus notes client ID re-certification process.






Please see the below careful if you are not clear the above steps.
Administrator: Recertify user's ID
A user has a Notes ID that has an expired certificate. These steps are performed by the server administrator to correct the user's expired ID.
  1. After obtaining the user ID, you (as the administrator) launch the Lotus® Domino® Administration client.
  2. Open the Configuration tab, expand Certification (located on the right hand pane) and select Certify.
  3. Select the Certifier ID file.
  4. From the Choose Certifier ID dialog box, select the O or OU certifier that was originally used to certify the user ID.
  5. Enter the password for the certifier ID.
  6. From the Choose ID to Certify dialog box, select the user ID to be recertified.
  7. Enter the password for user ID to be recertified.
  8. [Optional] In the Certify ID dialog box, you may set or change the following:
    Registration server, expiration date of the certifier and password length.
  9. Click Certify.
    The Status window displays:
    Updating address book entry for username/org
    Successfully updated address book entry for username/org
    Username/org successfully certified
  10. Choose "No" when you receive the following dialog box:
    Would you like to certify another?
  11. Provide the newly-recertified ID file to the user.

User: Merge the new certificate
Once the administrator recertifies the safe.ID and returns the ID to the user, the user must perform the following steps:
  1. Select File -> Security -> User Security -> Your Identity -> Your Certificates -> Get certificates button -> Import (Merge) Notes Certificate.
  2. Enter password.
  3. The dialog box then prompts the user to choose the safe.ID that has been recertified and it is then merged into the original user ID.

Comments

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...