How does HTTPS work?

 Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP.) HTTPS transmits encrypted data using Transport Layer Security (TLS.) If the data is hijacked online, all the hijacker gets is binary code.

How is the data encrypted and decrypted?

Step 1 - The client (browser) and the server establish a TCP connection.

Step 2 - The client sends a “client hello” to the server. The message contains a set of necessary encryption algorithms (cipher suites) and the latest TLS version it can support. The server responds with a “server hello” so the browser knows whether it can support the algorithms and TLS version.

The server then sends the SSL certificate to the client. The certificate contains the public key, host name, expiry dates, etc. The client validates the certificate.

Step 3 - After validating the SSL certificate, the client generates a session key and encrypts it using the public key. The server receives the encrypted session key and decrypts it with the private key.

Step 4 - Now that both the client and the server hold the same session key (symmetric encryption), the encrypted data is transmitted in a secure bi-directional channel

Why does HTTPS switch to symmetric encryption during data transmission? There are two main reasons:

1. Security: The asymmetric encryption goes only one way. This means that if the server tries to send the encrypted data back to the client, anyone can decrypt the data using the public key.

2. Server resources: The asymmetric encryption adds quite a lot of mathematical overhead. It is not suitable for data transmissions in long sessions.Over to you: how much performance overhead does HTTPS add, compared to HTTP?

How does SSO Work - Thanks to bytebytego.com

 

Step 1: A user visits Gmail, or any email service. Gmail finds the user is not logged in and so redirects them to the SSO authentication server, which also finds the user is not logged in. As a result, the user is redirected to the SSO login page, where they enter their login credentials.

Steps 2-3: The SSO authentication server validates the credentials, creates the global session for the user, and creates a token.

Steps 4-7: Gmail validates the token in the SSO authentication server. The authentication server registers the Gmail system, and returns “valid.” Gmail returns the protected resource to the user.

Step 8: From Gmail, the user navigates to another Google-owned website, for example, YouTube. 

Steps 9-10: YouTube finds the user is not logged in, and then requests authentication. The SSO authentication server finds the user is already logged in and returns the token.

Step 11-14: YouTube validates the token in the SSO authentication server. The authentication server registers the YouTube system, and returns “valid.” YouTube returns the protected resource to the user.

The process is complete and the user gets back access to their account.

Front End Development Roadmap

 

Top DevOps Tools

 

COTS VS SaaS

 

• The primary reason most enterprises are moving to a SaaS solution due to the fact that it is perceived on being financially more attractive.
• Comparison between the license costs of a COTS solution and the costs involved consuming a SaaS service.
• As typically COTS software is software that you need to install, configure and manage yourself. Whereas SaaS is something you consume and the SaaS provider is responsible for a lot of stuff.

------------------------------------------------------------------------------------------------------

1) Licensing / Costs SaaS is a deployment strategy, not a licensing strategy. However, many SaaS solutions are sold on a subscription basis, enabling companies to avoid the significant upfront license fees. This can enable organizations to manage SaaS purchases as operational expenses instead of cap ex and get more bang for the buck. Organizations should also factor the savings from infrastructure, support resources, and software maintenance fees

2)Customizations While SaaS has come a long way in terms of allowing customers to configure new fields, change processing rules and even develop bolt-on applications using their platform, they do not come close to allowing the level of customizations in traditional packaged on premise software. SaaS solutions have to account for enabling seamless upgrades without customer involvement. This requires the vendors to place limits on the ability to modify data models, programming, etc within the application. If your business demands significant customizations SaaS is not right for you. In the next part in the series we will wrap up our SaaS review.

Pros :

1. Lower TCO

2. Large Capablity Set

3. Allow small customizations through the software's configuration

4. Financially more attractive.

5. Allows customer to try before they buy.

Cons :

1. More training Required 

2. Have to Adjust the business according to the software

3. 

Cloud Computing VS Cloud Native

 "Cloud computing” is when CSP runs your server.

“Cloud native” is when CSP runs your code.

A reference architecture for multicloud

 

Data-focused multicloud deals with everything that’s stored inside and outside of the public clouds. Cloud-native databases exist here, as do legacy databases that still remain on-premises. The idea is to manage these systems using common layers, such as management and monitoring, security, and abstraction. 

Service-focused multicloud means that we deal with behavior/services and the data bound to those services from the lower layers of the architecture. It’s pretty much the same general idea as data-focused multicloud, in that we develop and manage services using common layers of technology that span from the clouds back to the enterprise data center.