Synapse - ADLS - Spark Notebook - Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired.

Question

Synapse - ADLS - Spark Notebook - Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired.

Andrii Shymko 0

Hello!

We use PySpark code in Synapse Notebook to read files from ADLS Gen2. For that we use mssparkutils.credentials.getSecret() and mssparkutils.credentials.getConnectionStringOrCreds() commands (see below)

account_access_key = mssparkutils.credentials.getSecret(akvName, secretName, linkedService)
...
sas_token = mssparkutils.credentials.getConnectionStringOrCreds(linkedService)

The necessary access like Storage Blob Data Contributor are provided to the Synapse Service principle. The Pipeline with the PySpark code notebook worked fine for 2.5 months, but recently the notebook in the pipeline is failed with the following error:

Py4JJavaError: An error occurred while calling z:mssparkutils.credentials.getSecret. : com.microsoft.azure.synapse.tokenlibrary.TokenLibrary$NonRetryableStatusException$1: POST failed with 'Unauthorized' (401) and message: {"result":"UserError","errorId":"Unauthorized","errorMessage":"Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '8/12/2023 11:52:43 PM', Current time (UTC): '8/17/2023 12:54:55 PM'.. TraceId : 92f6a324-04ff-45c1-aa5e-d03c57f78179 | client-request-id : 55e09202-c679-4d0a-ac11-54c907c5b9ba. Error Component : TokenService"} 	at com.microsoft.azure.synapse.tokenlibrary.TokenLibrary.$anonfun$invokeTokenService$7(TokenLibrary.scala:470) 	at com.twitter.util.Future.$anonfun$flatMap$1(Future.scala:1808) 	at com.twitter.util.Promise$FutureTransformer.liftedTree1$1(Promise.scala:240) 	at com.twitter.util.Promise$FutureTransformer.k(Promise.scala:240) 	at com.twitter.util.Promise$Transformer.apply(Promise.scala:215) 	at com.twitter.util.Promise$WaitQueue.com$twitter$util$Promise$WaitQueue$$run(Promise.scala:91) 	at com.twitter.util.Promise$WaitQueue$$anon$1.run(Promise.scala:86) 	at com.twitter.concurrent.LocalScheduler$Activation.run(Scheduler.scala:198) 	at com.twitter.concurrent.LocalScheduler$Activation.submit(Scheduler.scala:157) 	at com.twitter.concurrent.LocalScheduler.submit(Scheduler.scala:274) 	at com.twitter.concurrent.Scheduler$.submit(Scheduler.scala:109) 	at com.twitter.util.Promise$WaitQueue.runInScheduler(Promise.scala:86) 	at com.twitter.util.Promise.updateIfEmpty(Promise.scala:778) 	at com.twitter.util.Promise.update(Promise.scala:750) 	at com.twitter.util.Promise.setValue(Promise.scala:726) 	at com.twitter.concurrent.AsyncQueue.offer(AsyncQueue.scala:123) 	at com.twitter.finagle.netty4.transport.ChannelTransport$$anon$2.channelRead(ChannelTransport.scala:168) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.UnpoolHttpHandler$.channelRead(UnpoolHttpHandler.scala:32) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.ClientExceptionMapper$.channelRead(ClientExceptionMapper.scala:35) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.HeaderValidatorHandler$.channelRead(HeaderValidatorHandler.scala:51) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438) 	at shadenetty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323) 	at shadenetty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297) 	at shadenetty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.ssl.SslHandler.unwrap(SslHandler.java:1432) 	at shadenetty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1199) 	at shadenetty.handler.ssl.SslHandler.decode(SslHandler.java:1243) 	at shadenetty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:502) 	at shadenetty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:441) 	at shadenetty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) 	at shadenetty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500) 	at shadenetty.channel.nio.NioEventLoop.run(NioEventLoop.java:462) 	at shadenetty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at com.twitter.finagle.util.BlockingTimeTrackingThreadFactory$$anon$1.run(BlockingTimeTrackingThreadFactory.scala:23) 	at shadenetty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) 	at java.lang.Thread.run(Thread.java:750)

The Linked Service has "Account key" authentication type. I checked Linked Service connection and it works properly.

I created a new Linked Service with another type of authentication ("System Assigned Managed Identity") and used instead of the existing one but the same issue occurred.

Please help me to understand a root cause of this issue.

Thank you in advance!

PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-18T06:05:04.1166667+00:00

@Anonymous - Thanks for the question and using MS Q&A platform.

The error message indicates that the certificate associated with the JobSessionToken has expired. This could be due to the fact that the certificate has not been renewed or updated. You can try to renew or update the certificate and see if that resolves the issue.

From the error message: Py4JJavaError: An error occurred while calling z:mssparkutils.credentials.getSecret. : com.microsoft.azure.synapse.tokenlibrary.TokenLibrary$NonRetryableStatusException$1: POST failed with 'Unauthorized' (401) and message: {"result":"UserError","errorId":"Unauthorized","errorMessage":"Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '8/12/2023 11:52:43 PM', Current time (UTC): '8/17/2023 12:54:55 PM' - the key has been expired on 8/12/2023.

Also, you mentioned that you created a new Linked Service with another type of authentication ("System Assigned Managed Identity") and used it instead of the existing one but the same issue occurred. This suggests that the issue may not be related to the Linked Service authentication type.

You can try to check if the necessary access like Storage Blob Data Contributor are still provided to the Synapse Service principle. If not, you can grant the required access and see if that resolves the issue.

If the issue persists, you can try to open a support ticket for further assistance.

Hope this helps. Do let us know if you any further queries.
Andrii Shymko 0 Reputation points

2023-08-18T07:47:15.91+00:00

Thanks for your reply!

One more thing. I would be very grateful if you could point me to the place in Azure where I can find the certificate associated with the JobSessionToken.
Andrii Shymko 0 Reputation points

2023-08-18T07:49:02.9733333+00:00

Thanks for your reply!

One more thing. I would be very grateful if you could point me to the place in Azure where I can find the certificate associated with the JobSessionToken.
Andrii Shymko 0 Reputation points

2023-08-21T08:31:18.43+00:00

Hello!

One more thing, Azure services Region is Qatar. Probably, this does mater.

It would be great if you can provide a link to create appropriate Microsoft support ticket.

Thank you!
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-22T08:46:14.4333333+00:00

@Anonymous - Thanks for the details.

I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us?

For more details, refer to Create an Azure support request.
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-28T04:54:27.3066667+00:00

@Anonymous - Did you get a chance to open a support ticket?
Andrii Shymko 0 Reputation points

2023-08-28T17:32:46.9933333+00:00

Hi,

Yes, I created the support request 2308240050002132.

The issue is resolved. But need to get more info from our DevOps team about the solution itself cause I don't know what specific steps are done.

I'll let you know as soon as I have these details.
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-31T05:08:13.9566667+00:00

@Anonymous - Thanks for sharing the support request number. Post resolving the issue with the help of support, kindly share the solution, which might be beneficial to other community members reading this thread.
Andrii Shymko 0 Reputation points

2023-09-12T14:40:04.9733333+00:00

Hello,

The issue was auto-resolved. I did nothing with Azure App registration (we don't have any Azure App registrations) or any other steps to fix this problem.

I only know that the issue was related to Asymmetric X509 certificate expiration.

Thus, a root cause of this issue is still unclear to me.

1 answer

Your answer

PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-18T06:05:04.1166667+00:00

@Anonymous - Thanks for the question and using MS Q&A platform.

The error message indicates that the certificate associated with the JobSessionToken has expired. This could be due to the fact that the certificate has not been renewed or updated. You can try to renew or update the certificate and see if that resolves the issue.

From the error message: Py4JJavaError: An error occurred while calling z:mssparkutils.credentials.getSecret. : com.microsoft.azure.synapse.tokenlibrary.TokenLibrary$NonRetryableStatusException$1: POST failed with 'Unauthorized' (401) and message: {"result":"UserError","errorId":"Unauthorized","errorMessage":"Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '8/12/2023 11:52:43 PM', Current time (UTC): '8/17/2023 12:54:55 PM' - the key has been expired on 8/12/2023.

Also, you mentioned that you created a new Linked Service with another type of authentication ("System Assigned Managed Identity") and used it instead of the existing one but the same issue occurred. This suggests that the issue may not be related to the Linked Service authentication type.

You can try to check if the necessary access like Storage Blob Data Contributor are still provided to the Synapse Service principle. If not, you can grant the required access and see if that resolves the issue.

If the issue persists, you can try to open a support ticket for further assistance.

Hope this helps. Do let us know if you any further queries.
Andrii Shymko 0 Reputation points

2023-08-18T07:47:15.91+00:00

Thanks for your reply!

One more thing. I would be very grateful if you could point me to the place in Azure where I can find the certificate associated with the JobSessionToken.
Andrii Shymko 0 Reputation points

2023-08-18T07:49:02.9733333+00:00

Thanks for your reply!

One more thing. I would be very grateful if you could point me to the place in Azure where I can find the certificate associated with the JobSessionToken.
Andrii Shymko 0 Reputation points

2023-08-21T08:31:18.43+00:00

Hello!

One more thing, Azure services Region is Qatar. Probably, this does mater.

It would be great if you can provide a link to create appropriate Microsoft support ticket.

Thank you!
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-22T08:46:14.4333333+00:00

@Anonymous - Thanks for the details.

I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us?

For more details, refer to Create an Azure support request.
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-28T04:54:27.3066667+00:00

@Anonymous - Did you get a chance to open a support ticket?
Andrii Shymko 0 Reputation points

2023-08-28T17:32:46.9933333+00:00

Hi,

Yes, I created the support request 2308240050002132.

The issue is resolved. But need to get more info from our DevOps team about the solution itself cause I don't know what specific steps are done.

I'll let you know as soon as I have these details.
PRADEEPCHEEKATLA 90,661 Reputation points Moderator

2023-08-31T05:08:13.9566667+00:00

@Anonymous - Thanks for sharing the support request number. Post resolving the issue with the help of support, kindly share the solution, which might be beneficial to other community members reading this thread.
Andrii Shymko 0 Reputation points

2023-09-12T14:40:04.9733333+00:00

Hello,

The issue was auto-resolved. I did nothing with Azure App registration (we don't have any Azure App registrations) or any other steps to fix this problem.

I only know that the issue was related to Asymmetric X509 certificate expiration.

Thus, a root cause of this issue is still unclear to me.

Answer 1

@Anonymous - I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

Issue: Synapse - ADLS - Spark Notebook - Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired.

Error:

Py4JJavaError: An error occurred while calling z:mssparkutils.credentials.getSecret. : com.microsoft.azure.synapse.tokenlibrary.TokenLibrary$NonRetryableStatusException$1: POST failed with 'Unauthorized' (401) and message: {"result":"UserError","errorId":"Unauthorized","errorMessage":"Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '8/12/2023 11:52:43 PM', Current time (UTC): '8/17/2023 12:54:55 PM'.. TraceId : 92f6a324-04ff-45c1-aa5e-d03c57f78179 | client-request-id : 55e09202-c679-4d0a-ac11-54c907c5b9ba. Error Component : TokenService"} 	at com.microsoft.azure.synapse.tokenlibrary.TokenLibrary.$anonfun$invokeTokenService$7(TokenLibrary.scala:470) 	at com.twitter.util.Future.$anonfun$flatMap$1(Future.scala:1808) 	at com.twitter.util.Promise$FutureTransformer.liftedTree1$1(Promise.scala:240) 	at com.twitter.util.Promise$FutureTransformer.k(Promise.scala:240) 	at com.twitter.util.Promise$Transformer.apply(Promise.scala:215) 	at com.twitter.util.Promise$WaitQueue.com$twitter$util$Promise$WaitQueue$$run(Promise.scala:91) 	at com.twitter.util.Promise$WaitQueue$$anon$1.run(Promise.scala:86) 	at com.twitter.concurrent.LocalScheduler$Activation.run(Scheduler.scala:198) 	at com.twitter.concurrent.LocalScheduler$Activation.submit(Scheduler.scala:157) 	at com.twitter.concurrent.LocalScheduler.submit(Scheduler.scala:274) 	at com.twitter.concurrent.Scheduler$.submit(Scheduler.scala:109) 	at com.twitter.util.Promise$WaitQueue.runInScheduler(Promise.scala:86) 	at com.twitter.util.Promise.updateIfEmpty(Promise.scala:778) 	at com.twitter.util.Promise.update(Promise.scala:750) 	at com.twitter.util.Promise.setValue(Promise.scala:726) 	at com.twitter.concurrent.AsyncQueue.offer(AsyncQueue.scala:123) 	at com.twitter.finagle.netty4.transport.ChannelTransport$$anon$2.channelRead(ChannelTransport.scala:168) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.UnpoolHttpHandler$.channelRead(UnpoolHttpHandler.scala:32) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.ClientExceptionMapper$.channelRead(ClientExceptionMapper.scala:35) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at com.twitter.finagle.netty4.http.handler.HeaderValidatorHandler$.channelRead(HeaderValidatorHandler.scala:51) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438) 	at shadenetty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323) 	at shadenetty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297) 	at shadenetty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.handler.ssl.SslHandler.unwrap(SslHandler.java:1432) 	at shadenetty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1199) 	at shadenetty.handler.ssl.SslHandler.decode(SslHandler.java:1243) 	at shadenetty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:502) 	at shadenetty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:441) 	at shadenetty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) 	at shadenetty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1434) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) 	at shadenetty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) 	at shadenetty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:965) 	at shadenetty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:648) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:583) 	at shadenetty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:500) 	at shadenetty.channel.nio.NioEventLoop.run(NioEventLoop.java:462) 	at shadenetty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at com.twitter.finagle.util.BlockingTimeTrackingThreadFactory$$anon$1.run(BlockingTimeTrackingThreadFactory.scala:23) 	at shadenetty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) 	at java.lang.Thread.run(Thread.java:750)

Solution: The issue was auto-resolved. I did nothing with Azure App registration (we don't have any Azure App registrations) or any other steps to fix this problem.

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

I hope this helps!

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

Share via

Synapse - ADLS - Spark Notebook - Invalid JobSessionToken : IDX10249: X509SecurityKey validation failed. The associated certificate has expired.

1 answer

Your answer