Комментарии:
👍🏼👍🏼
ОтветитьThank you! this is so well explained ☺
ОтветитьExcellent info thanks Laith.
ОтветитьGreat content! I thoroughly enjoyed your explanation; it was simple and easy to understand. Keep up the fantastic work!
ОтветитьMicroservices course bro please ❤❤
ОтветитьFantastic as always. thanks for your useful tuts 💗
Ответитьcompleted !!! to be honest never seen such a wonderful explanation on such complex topic
Regard: Kim from Pakistan
just watched your nginx course, you're really good at explaining man!
definitely gonna watch more of your videos
I love your teaching style. Do you have interest in sharing one of your already made courses with our channel?
ОтветитьThanks! You work for hello fresh, this is so cool!
I'm revisiting this process, it has been a while since i saw it at college. This is more complicated than i remember, but basically the CA Authority is encrypting an already public server key not to protect against decryption, but it is doing for the purpose of signature, because only the CA Authority could have ever issued an encrypted 'thing' that can be decrypted with the CA Authority public key. And we can check that the 'thing' after the decryption is correct because it is attached to the certificate. This very cool and well explained, appreciate the video.
And if you read this please correct me if my understand is wrong on this.
Can you make a video how sso and saml works in details also how to setup these in Google
Ответитьbravo much appreciated
ОтветитьGreat details, thanks. 🙂
ОтветитьThank you!
Ответить