I am not alarmed about the rising talent migration from India. Here is why.
First, historic patterns. Talent migration from Korea/Taiwan to the US peaked in the 1970s and 80s (Japanese migration to the US peaked much earlier), talent migration from China peaked about 10 years ago. That was the time of rapid development and transformation of those nations.
When a country is extremely underdeveloped, talent migration is very low. When a country is very wealthy, talent migration is also very low. Talent migration peaks during the period of rapid development.
This is observable in silicon valley where migrants from India now well outpace those from China, Hong Kong and Taiwan.
Why does this happen? Rapid economic development is preceded by and happens due to rising aspiration levels; and talent migration also happens due to rising aspiration levels. Our aspirations necessarily race ahead of reality and it is precisely during the period of rapid growth that we have the most restless people, and it is the restless spirits who tend to migrate. We can observe that restlessness in India, particularly in urban tech centres.
Eventually when the full economic potential is realised, talent migration slows down or stops entirely. This pattern has been seen repeatedly.
As late as the 1980s, Japanese still refused to believe Japan had achieved parity with the West. Same with Korea in the late 1990s. I predict that even in 2035 with a per capita GDP upwards of $10K, Indians will likely lament how far behind we are. The last stage of catch up happens quickly over a decade (witness China is the last decade) but the foundations have to be laid over many previous decades and those previous decades feel like a slog. We are slogging through that now in India.
To summarise, rising talent migration from India is not a symptom of hopelessness, it is the opposite.
Be an optimist! 🙏
SSO (Single Sign-On) Explained.
SSO can be thought of as a master key to open all different locks. It allows a user to log in to different systems using a single set of credentials.
In a time where we are accessing more applications than ever before, this is a big help to mitigate password fatigue and streamlines user experience.
To fully understand the SSO process, 𝗹𝗲𝘁’𝘀 𝘁𝗮𝗸𝗲 𝗮 𝗹𝗼𝗼𝗸 𝗮𝘁 𝗵𝗼𝘄 𝗮 𝘂𝘀𝗲𝗿 𝘄𝗼𝘂𝗹𝗱 𝗹𝗼𝗴 𝗶𝗻𝘁𝗼 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻 𝘂𝘀𝗶𝗻𝗴 𝗚𝗼𝗼𝗴𝗹𝗲 𝗮𝘀 𝘁𝗵𝗲 𝗶𝗱𝗲𝗻𝘁𝗶𝘁𝘆 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿:
𝟭) 𝗨𝘀𝗲𝗿 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀 𝗮𝗰𝗰𝗲𝘀𝘀
First, the user would attempt to access the Service Provider (LinkedIn). At this point, a user would be presented with login options, and in this example, they would select "Sign in with Google".
𝟮) 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗿𝗲𝗾𝘂𝗲𝘀𝘁
From here, the Service Provider (LinkedIn) will redirect the user to the Identity Provider (Google) with an authentication request.
𝟯) 𝗜𝗱𝗣 𝗰𝗵𝗲𝗰𝗸𝘀 𝗳𝗼𝗿 𝗮𝗰𝘁𝗶𝘃𝗲 𝘀𝗲𝘀𝘀𝗶𝗼𝗻
Once the Identity Provider (Google) has received the request, it will check for an active session. If it doesn't find one, authentication will be requested.
𝟰) 𝗨𝘀𝗲𝗿 𝘀𝘂𝗯𝗺𝗶𝘁𝘀 𝗰𝗿𝗲𝗱𝗲𝗻𝘁𝗶𝗮𝗹𝘀
At this stage, the user will submit their login credentials (username and password) to the Identity Provider (IdP).
𝟱) 𝗜𝗱𝗣 𝘃𝗲𝗿𝗶𝗳𝗶𝗲𝘀 𝗰𝗿𝗲𝗱𝗲𝗻𝘁𝗶𝗮𝗹𝘀
The Identity Provider will then verify the submitted credentials against its User Directory (database). If the credentials are correct, the IdP will create an authentication token or assertion.
𝟲) 𝗜𝗱𝗣 𝘀𝗲𝗻𝗱𝘀 𝘁𝗼𝗸𝗲𝗻 𝘁𝗼 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗣𝗿𝗼𝘃𝗶𝗱𝗲𝗿
Once the token or assertion has been created, the IdP sends it back to the Service Provider confirming the user's identity. The user is now authenticated and can access the Service Provier (LinkedIn).
𝟳) 𝗔𝗰𝗰𝗲𝘀𝘀 𝗴𝗿𝗮𝗻𝘁𝗲𝗱 𝘂𝘀𝗶𝗻𝗴 𝗲𝘅𝗶𝘀𝘁𝗶𝗻𝗴 𝘀𝗲𝘀𝘀𝗶𝗼𝗻
Since the Identity Provider has established a session, when the user goes to access a different Service Provider (eg; GitHub), they won't need to re-enter their credentials. Future service providers will request authentication from the Identity Provider, recognize the existing session, and grant access to the user based on the previously authenticated session.
SSO workflows like the above operate on SSO protocols, which are a set of rules that govern how the IdP and SP communicate and trust each other. Common protocols include Security Assertion Markup Language (SAML), OpenID Connect, and OAuth.
@Flipkart@flipkartsupport@_Kalyan_K it seems you are not following up this is 2nd time im posting still no response shame on you. Can your team eloberate how you ppl are working on this issue to get fixed??
OrderID -OD429379465880322100 i have placed order on oct10. It has been more than 10days still not delivered and no response from support as well what a shame for on you flipkart .Do care about your customers .let us know the exact delivery date @Flipkart@flipkartsupport
Here’s a compilation of Personal Finance threads I have written so far. Thank you for motivating me to do it.
Hit the 're-tweet' and help us educated more investors
Should you buy Sovereign Gold Bond (SGB)? If yes, should you buy the new tranche at 5561 or some older listed tranche & which one of the 62 tranches issued so far & why? A detailed 🧵 👇
Do ‘re-tweet’ & help us educate more investors (1/22)