×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

SMGR

SMGR

(OP)
I'm running SMGR 7.0.x and I've seen an event in log referencing weblm legacy cert expiring. We install our own CA's trusted certs in the trust stores of SMGR and ASM and use our own Identity certs on ASM. Looking through the managed elements it shows the weblm legacy cert is expired. I gather it's not relevant because nothing has went crackers. I went through the managed elements and in the SMGR trust store I do see a few of the following that have long expired.

Used for validating TLS server identity certificates TM_OUTBOUND_TLS CN=Avaya Client Services Users CA, OU=Avaya IT, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Symantec Trust Network, O="Avaya, Inc.", C=US

Used for validating TLS server identity certificates TM_OUTBOUND_TLS CN="Avaya CA C=US O=Avaya"

Used for validating TLS server identity certificates TM_OUTBOUND_TLS CN=ESDP CA, OU=Avaya Global Services, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Terms of use at https://www.verisign.com/rpa (c)06, OU=VeriSign Trust Network, O="Avaya, Inc.", C=US

Used for validating TLS server identity certificates TM_OUTBOUND_TLS CN=ESDP CA, OU=Avaya Global Services, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Terms of use at https://www.verisign.com/rpa (c)06, OU=VeriSign Trust Network, O="Avaya, Inc.", C=US

Used for validating TLS client identity certificates TM_INBOUND_TLS_PEM CN=ESDP CA, OU=Avaya Global Services, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Terms of use at https://www.verisign.com/rpa (c)06, OU=VeriSign Trust Network, O="Avaya, Inc.", C=US

Used for validating TLS client identity certificates TM_INBOUND_TLS CN=Avaya Client Services Users CA, OU=Avaya IT, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Symantec Trust Network, O="Avaya, Inc.", C=US

Used for validating TLS client identity certificates TM_INBOUND_TLS CN=ESDP CA, OU=Avaya Global Services, OU=Class 2 Managed PKI Individual Subscriber CA, OU=Terms of use at https://www.verisign.com/rpa (c)06, OU=VeriSign Trust Network, O="Avaya, Inc.", C=U

Again, nothing has gone crackers on the system and these above certs expired years ago.

I raised a ticket with Avaya and they are pointing at a PSN where they need to run a script that does something with auto-renewal of certs. Is this necessary to do based on what I'm seeing? The engineer is saying they cannot do this out of hours/weekend and I'm concerned whatever this script is going to do will blow up the certs we installed on this. Anyone face this before?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close