#YOUVIEW BOOT FAIL INVALID SIGNATURE WINDOWS#

500 http error Signed JWT rejected: Invalid signatureД¬rashing with the Signed JWT rejected: Invalid signature.Obtain an access token using with OIDC & AAD.But when trying to use it with that spring boot apps that faces all incoming requests we keep getting that weird message Signed JWT rejected: Invalid signature Reproduce steps

When manually trying to authenticate on the graph api using postman with /me with the Token Bearer it works perfectly. configuration utilized openid as a scope. # from /etc/grub.When trying to use the authentication endpoints we are getting Signed JWT rejected: Invalid signature, we are currently in a setup where does a callout rest request to an external app that is secured by AAD springboot starter. # It is automatically generated by grub-mkconfig using templates

#YOUVIEW BOOT FAIL INVALID SIGNATURE WINDOWS#

Use the way chainloading is setup for Windows as a guide. I think you will have to hand-craft that section of the configuration. Create a chain-loader section of your grub configuration, so that the grub2-efi (from opensuse) chainloads to the grub2-efi installed by ubuntu, when loading ubuntu.

Use the grub installed with Ubuntu to handle the booting.

At some future time, Ubuntu may make the same fixes, and then Ubuntu won't be able to boot opensuse. That weakness was fixed for opensuse 13.1, and now you can't do it. That you could load a kernel, without checking its signature, was seen as a weakness in the secure-boot support. I'm guessing that ubuntu is doing that to load opensuse. With opensuse 12.3, it was possible to use secure-boot to load 'shim.efi', and then to configure grub so that 'shim.efi' did not check signatures of the kernels that it loaded. If that is incorrect I'm still wondering how ubuntu manages to boot suse but not vice-versaIt could have worked both ways with opensuse 12.3, but not with 13.1.

Youview boot fail invalid signature