Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Table of Contents

Key Points


References

Reference_description_with_linked_URLs_______________________Notes______________________________________________________________














...

FEMA Issues Survival Guide Amid Fears Of Nuclear Attack - 241204

three crucial steps: Get Inside, Stay Inside, and Stay Tuned

https://www.fema.gov/emergency-managers/national-preparedness/plan


https://emptaskforce.us/




TrustGrid Concepts


TrustGrid and Heale partner on Logistics Supply Chain

...

Potential Value Opportunities


DePIN- Decentralized Physical Infrastrcture Networks for DeFi VCE - 2025

depin-crypto-infrastructure-solutions-status.pdf

Image Added



Potential Challenges



Candidate Solutions

...

SSO - Single Signon to multiple sites using same credentials ( Kerberos ticket granting server model )

Open ID Connect - 

How OpenID Connect SSO Works? OpenID Connect will redirect a user to an identity provider (IdP) to check the user's identity, either by looking for an active session i.e Single Sign-On (SSO) or by asking the user to authenticate.

OpenID Connect (OIDC) is an identity authentication protocol that is an extension of open authorization (OAuth) 2.0 to standardize the process for authenticating and authorizing users when they sign in to access digital services. OIDC provides authentication, which means verifying that users are who they say they are. OAuth 2.0 authorizes which systems those users are allowed to access. OAuth 2.0 is typically used to enable two unrelated applications to share information without compromising user data. For example, many people use their email or social media accounts to sign in to a third-party site rather than creating a new username and password. OIDC is also used to provide single sign-on. Organizations can use a secure identity and access management (IAM) system like Microsoft Entra ID (formerly Azure Active Directory) as the primary authenticator of identities and then use OIDC to pass that authentication to other apps. This way users only need to sign in once with one username and password to access multiple apps.


Key Tools


Scaffolding >. Feathers, Loopback, Openapi

...