Nor mputao...

next

[Vallejowsky @vallejowsky]

¿Otra vez hemos comprado papel higiénico en vano?

[La Abuela García®™ @rthur013]

La mayoría de la peleas de parejas, terminan así 😅😅😅😅...

[Nathaly Alarcón Torrico @NathalyAlarconT]

¡Buenas noticias! Google lanzó #Gemma, una familia de potentes modelos abiertos de #GenAI. Ahora puedes usarlos fácilmente en tus aplicaciones.

Te comparto un tutorial sencillo con todo lo necesario que necesitas para empezar a usarlo🤓🤖
https://t.co/wvudcsXv8t
#ML

[Leona @Leonaypeleona]

Gente querida de esta red, algunos saben que durante la pandemia empecé un emprendimiento que me hizo muy feliz, aunque voy a retomarlo por ahora estoy liquidando todo! Así que aprovechen para tener lindos regalos por el Día de la Madre o para ustedes!

[Kirk Borne @KirkDBorne]

This GitHub repository contains everything you need to become proficient in System Design with 200+ system design case studies: https://t.co/iLL2My5MRo by @NainaChaturved8

[Nor mputao... @normmy2k]

@sopocachi_org No cantes Victoria

[El Programador Senior @5eniorDeveloper]

Cuando solo tienes el mockup, pero el cliente insiste que quiere una demo

[nixCraft 🐧 @nixcraft]

Freenginx: Core Nginx developer announces fork

[vdecrypto @vdecrypto]

Hoy vamos a ver cómo eliminar tu información personal de Internet.

Dentro de hilo 👇🧵

[nixCraft 🐧 @nixcraft]

Everyone has a test environment, some people are lucky enough that they have a separate one for running prod

[El Programador Senior @5eniorDeveloper]

No sé qué haríamos sin nuestro líder 🤣

[Nor mputao... @normmy2k]

@Sysivel Estas más capacitada que el alcalde.

[El Programador Senior @5eniorDeveloper]

Y te dicen: tanto tiempo para eso?

[nixCraft 🐧 @nixcraft]

Satan: You can have anything you wan...

Me: Programming language.

Satan: What?

Me: Give me all Programming language and related knowledge.

Satan: What the hell?

Me: YOU SAID ANYTHING. I WANT TO KNOW ALL PROGRAMMING LANGUAGES.

Satan: Wouldn't you rather have love or money in your depressed life?

Me: EVERY. PROGRAMMING LANGUAGES. NO NEED TO READ DOCS, ChatGPT, OR GOOGLE ANYTHING. ALL KNOWLEDGE ABOUT ALL PROGRAMMING LANGUAGES, AI, ML, AND DATA STRUCTURES. NOW.

[Dios @diostuitero]

Hoy es mi cumpleaños. Para conmemorar la llegada de un niño pobre que vino a salvar al mundo, os pasáis dos semanas enteras promoviendo el consumismo, la ingesta de alcohol y comida sin medida y la ludopatía. Empiezo a pensar que no pillásteis mi mensaje.

[Nor mputao... @normmy2k]

@semptrion Mientras comenté esto la Contraloría ya comienza con las auditorias de los planes de implementación de SL, ya se habla de responsabilidades a las MAES. Pero quizá no estés listo para esta conversación...

[Nor mputao... @normmy2k]

@ErwinQuispePerk Usted si sabe, tome mi like!

[Nor mputao... @normmy2k]

@nah_omy Y peor a fin de año

[Nor mputao... @normmy2k]

@ramirocamacho1 @laverde_fbf @CopaAmerica Muy interesante la propuesta! Especialmente Justiniano q solo se dedica a golpear.

[Chris Staudinger @ChrisStaud]

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.