#singlesignon — Public Fediverse posts

Forcing employees to log in multiple times weakens their willingness to select secure login methods. Consequently, introducing Single Sign-On can go a long way to enhance cybersecurity.
#cybersecurity #singlesignon
https://www.forbes.com/councils/forbestechcouncil/2026/08/10/how-to-protect-retail-systems-as-cyber-risks-multiply/

Forcing employees to log in multiple times weakens their willingness to select secure login methods. Consequently, introducing Single Sign-On can go a long way to enhance cybersecurity.
#cybersecurity #singlesignon
https://www.forbes.com/councils/forbestechcouncil/2026/08/10/how-to-protect-retail-systems-as-cyber-risks-multiply/

Forcing employees to log in multiple times weakens their willingness to select secure login methods. Consequently, introducing Single Sign-On can go a long way to enhance cybersecurity.
#cybersecurity #singlesignon
https://www.forbes.com/councils/forbestechcouncil/2026/08/10/how-to-protect-retail-systems-as-cyber-risks-multiply/

Forcing employees to log in multiple times weakens their willingness to select secure login methods. Consequently, introducing Single Sign-On can go a long way to enhance cybersecurity.
#cybersecurity #singlesignon
https://www.forbes.com/councils/forbestechcouncil/2026/08/10/how-to-protect-retail-systems-as-cyber-risks-multiply/

Forcing employees to log in multiple times weakens their willingness to select secure login methods. Consequently, introducing Single Sign-On can go a long way to enhance cybersecurity.
#cybersecurity #singlesignon
https://www.forbes.com/councils/forbestechcouncil/2026/08/10/how-to-protect-retail-systems-as-cyber-risks-multiply/

Infinito.Nexus 12.0: From a Single Server to a Scalable Sovereign Cloud

https://blog.infinito.nexus/blog/2026/08/08/infinito-nexus-12-0-from-a-single-server-to-a-scalable-sovereign-cloud/

OpenAI is testing a 'Sign in with ChatGPT' feature across select platforms, enabling seamless single sign-on while preserving user account security.

#OpenAI #ChatGPT #SingleSignOn #Cybersecurity #WebDevelopment

https://securityonline.info/sign-in-with-chatgpt/?utm_source=mastodon&utm_medium=jetpack_social

Look at this! I was finally able to configure all of these apps to allow #SingleSignOn (#SSO) using #kanidm on #NixOS.

I admit I couldn't do this without the help of an #LLM (I used antigravity-cli for this). I know there are a lot of good points against LLMs, but they sure are really useful to me.

Look at this! I was finally able to configure all of these apps to allow #SingleSignOn (#SSO) using #kanidm on #NixOS.

I admit I couldn't do this without the help of an #LLM (I used antigravity-cli for this). I know there are a lot of good points against LLMs, but they sure are really useful to me.

Look at this! I was finally able to configure all of these apps to allow #SingleSignOn (#SSO) using #kanidm on #NixOS.

I admit I couldn't do this without the help of an #LLM (I used antigravity-cli for this). I know there are a lot of good points against LLMs, but they sure are really useful to me.

Look at this! I was finally able to configure all of these apps to allow #SingleSignOn (#SSO) using #kanidm on #NixOS.

I admit I couldn't do this without the help of an #LLM (I used antigravity-cli for this). I know there are a lot of good points against LLMs, but they sure are really useful to me.

Look at this! I was finally able to configure all of these apps to allow #SingleSignOn (#SSO) using #kanidm on #NixOS.

I admit I couldn't do this without the help of an #LLM (I used antigravity-cli for this). I know there are a lot of good points against LLMs, but they sure are really useful to me.

Stop Guessing, Start Measuring: The Cold Math of the Passphrase Transition

1,644 words, 9 minutes read time.

The Structural Collapse of the Legacy Password

The traditional eight-character alphanumeric password is a broken line of defense that offers nothing more than a false sense of security. For decades, users have been instructed to construct complex strings filled with uppercase letters, numbers, and obscure symbols, under the mistaken belief that this fragmentation creates an impenetrable barrier. The contemporary threat landscape has rendered these legacy methodologies entirely obsolete, as attackers no longer rely on manual guessing but on automated, high-velocity cryptographic assaults that exploit the inherent predictability of human patterns. To survive in this environment, enterprise architecture must shift toward the passphrase, a credential strategy rooted in length rather than fragmented complexity. This analytical deep dive will demonstrate that information entropy heavily favors length over a constrained character pool, proving that longer strings fundamentally break the mathematical models used by modern cracking tools. Furthermore, an examination of hardware acceleration will reveal how easily graphics processing units dismantle complex but short passwords through sheer processing volume. The analysis will also expose the human failure point, showing how predictable character substitutions actually aid automated dictionary attacks rather than hindering them. Finally, this post will outline the institutional shift led by regulatory frameworks that officially mandates the transition to high-entropy passphrases as a baseline security requirement.

Why Entropy Defeats Arbitrary Complexity

The security of any credential rests entirely on its mathematical entropy, which measures the total number of possible combinations an attacker must search through to guarantee a successful breach. Legacy security policies focused intensely on expanding the character pool by forcing users to mix uppercase letters, lowercase letters, numbers, and symbols, assuming this diversity would stall an attack. This logic fails because the total search space scales linearly when adding character types, but scales exponentially when increasing the overall length of the string. An eight-character password drawing from an expanded pool of ninety-four possible characters yields a search space that modern computing clusters can exhaust in a matter of hours. Conversely, a twenty-character passphrase composed exclusively of standard lowercase letters draws from a smaller pool of twenty-six characters, yet its sheer length creates a computational search space that is astronomically larger. The exponential power of length completely dwarfs the linear additions of complexity, making the long string mathematically superior in every measurable metric. Security is a game of resource depletion, and forcing an attacker to calculate permutations across a massive length consumes their time and computational power far more effectively than a short, complex puzzle. Relying on symbols to protect a short credential is a fundamental misunderstanding of cryptographic reality.

How Modern Computing Power Obliterates Standard Credentials

The rise of massive hardware acceleration has turned password cracking into an industrialized, automated process that operates at a scale most organizations fail to comprehend. Modern threat actors do not target live login portals where rate-limiting defenses exist; they exfiltrate hashed credential databases and conduct offline attacks using specialized graphics processing unit clusters. A single consumer-grade graphics card can execute billions of cryptographic hash calculations every second, and when multiple cards are parallelized, the throughput becomes devastatingly efficient. Legacy hashing algorithms that were once considered robust offer minimal resistance against this level of raw processing power when the target credential is short. A complex, eight-character password is reduced to a minor computational speed bump when confronted by an array capable of cycling through trillions of permutations in a single afternoon. Passphrases alter this dynamic entirely by forcing the attack automation to scale up its calculations to a point that becomes financially and logistically unviable for the adversary. When a credential possesses sufficient length, the time required to exhaust the mathematical possibilities extends from hours into decades, effectively neutralizing the advantage of hardware acceleration. Organizations that continue to permit short, complex credentials are explicitly ignoring the reality of modern computing capability and leaving their infrastructure vulnerable to rapid automated compromise.

The Illusion of Security in Character Substitution

Human psychology is inherently predictable, and when users are forced to create complex strings that defy natural memory retention, they invariably take shortcuts that automated attack tools are specifically designed to exploit. The common practice of replacing a letter with a lookalike number or symbol does not create randomness; it merely creates a predictable pattern that mirrors basic human behavior. Automated dictionary attacks do not guess randomly across the entire character space from the first second; they utilize highly sophisticated rule sets that automatically apply common substitutions to known words. This means an obfuscated password is often broken just as quickly as its plain-text counterpart because the underlying structure remains entirely unoriginal. Furthermore, forcing users to memorize these fragmented, unnatural strings leads directly to credential reuse across multiple platforms, creating a systemic risk where a single third-party breach compromises the entire enterprise. Passphrases solve this fundamental human vulnerability by leveraging words arranged in a sequence that is easy for a human to remember but entirely disjointed to an algorithm. By aligning credential policy with the way the human brain naturally retains information, organizations eliminate the need for dangerous substitutions and drastic reuse, creating a security model that functions in reality rather than only on paper.

Aligning Enterprise Standards with High-Entropy Passphrases

The transition from short, complex passwords to long passphrases is no longer a matter of structural debate; it is a formalized directive established by major global cybersecurity frameworks. The National Institute of Standards and Technology explicitly overhauled its digital identity guidelines to eliminate the legacy requirements for arbitrary character complexity and forced periodic expiration. Modern compliance frameworks recognize that frequent password changes and complex character mandates directly degrade security by encouraging predictable patterns and user fatigue. The updated standards heavily prioritize credential length, explicitly advising organizations to configure their identity providers to accept long strings while screening out known compromised entries. Implementing this architecture requires a deliberate reconfiguration of active directory environments, single sign-on platforms, and enterprise identity management systems to support minimum lengths of at least fifteen to twenty characters. Legacy applications that artificially restrict input length must be systematically updated or replaced, as they represent a critical vulnerability that prevents the enforcement of modern entropy standards. Failing to align enterprise architecture with these updated frameworks is a failure of technical oversight that leaves an organization legally and operationally exposed when a breach occurs.

The Definite Verdict on Credential Architecture

The data dictates a clear and uncompromising conclusion regarding enterprise credential policy. The legacy framework of short, complex passwords has utterly failed to withstand the realities of modern computing power, automated attack methodologies, and predictable human psychology. Information entropy proves that string length is the primary factor in resisting cryptographic attacks, while hardware acceleration has turned the cracking of short credentials into a trivial task. Human-generated substitutions offer zero protection against sophisticated dictionary rule sets, serving only to complicate user experience while leaving the underlying data vulnerable to exploitation. True security requires a complete rejection of outdated complexity mandates in favor of long, high-entropy passphrases that leverage exponential mathematical growth to exhaust attacker resources. Enterprise infrastructure must adapt immediately to these established standards to mitigate the threat of automated compromise and align with modern regulatory frameworks.

Enterprise identity architecture must be updated to enforce minimum lengths of fifteen to twenty characters to resist automated exploitation.

Information entropy mathematically favors credential length over character set complexity, creating exponentially larger search spaces.

Modern graphics processing unit clusters can rapidly exhaust short, complex credentials through high-velocity offline cracking.

Predictable human character substitutions fail to deceive modern automated dictionary attacks and encourage dangerous credential reuse.

Global security frameworks have officially shifted toward prioritizing length and eliminating arbitrary complexity mandates.

Audit Your Network: Secure Your Enterprise Infrastructure With High-Entropy Passphrases

Stop relying on an obsolete defense strategy that invites catastrophe. Audit your identity providers immediately, systematically dismantle the arbitrary complexity rules that compromise your user base, and configure your active directory to enforce a strict minimum threshold of fifteen or more characters. The transition to high-entropy passphrases is not an operational preference; it is an immediate cryptographic necessity to shield your enterprise from automated exploitation.

D. Bryan King

Sources

• NIST Special Publication 800-63B: Digital Identity Guidelines – Authentication and Lifecycle Management
• CISA: Protecting Against Brute Force Attacks
• CISA: Cyber Threats and Advisory Library
• MITRE ATT&CK: Brute Force Techniques (T1110)
• MITRE ATT&CK: Password Cracking (T1110.002)
• MITRE ATT&CK: Password Spraying (T1110.003)
• MITRE ATT&CK: Password Guessing (T1110.001)
• MITRE ATT&CK: Credential Stuffing (T1110.004)
• MITRE ATT&CK: Credentials from Password Stores (T1555)
• IEEE Xplore: Computational Metrics of Password Entropy
• IEEE Xplore: Analysis of Password Cracking Dynamics Using GPUs
• IEEE Xplore: Human Behavior Patterns in Alphanumeric Character Substitutions
• IEEE Xplore: Performance Optimization of Offline Dictionary Attacks
• OWASP: Password Creation Requirements Control Guidelines
• OWASP Top 10: Identification and Authentication Failures
• OWASP: Comprehensive Guide to Brute Force Attacks
• OWASP: Mechanics of Automated Credential Stuffing
• SANS Institute: The Mathematics of Length vs. Complexity
• SANS Institute: Defending Against Modern GPU Password Cracking Clusters
• SANS Institute: Rethinking Enterprise Password Expiration Policies
• SANS Institute: Implementation Strategies for High-Entropy Passphrases
• ENISA: Guidelines for Secure Password and Authentication Schemes
• Australian Cyber Security Centre (ACSC): Password Governance and Policies
• UK National Cyber Security Centre (NCSC): Password Policy Re-thought
• UK NCSC: Using Three Random Words for Strong Passphrases
• NIST Computer Security Resource Center: SP 800-63B Structural Reference
• BSI Germany: IT-Grundschutz Standards for Authentication
• ACM Digital Library: Analysis of Leaked Password Datasets and Substitution Rules
• ACM Digital Library: Guessing Human Passwords via Probabilistic Context-Free Grammars
• ACM Digital Library: The Security of Length-Based Passphrase Configurations
• ISO/IEC 27002: Information Security, Cybersecurity, and Privacy Protection Controls
• PCI DSS: Document Library for Identity and Access

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

The Double-Edged Sword of Digital Freedom: The Risks of Infinito.Nexus with Native Tor Support

⚠️ Disclaimer

This article was generated entirely by artificial intelligence without editorial review.

To publish this analysis quickly, I deliberately chose to release it without manual editing or fact-checking. The purpose of this article is not to provide a polished technical specification, but to stimulate discussion about the societal, ethical, and security implications of the next generation of Infinito.Nexus with native Tor support.

Some technical assumptions, predictions, or conclusions may therefore be incomplete, inaccurate, or open to debate. They should be understood as informed analysis rather than verified fact.

The scenarios described in this article are intended to illustrate both the opportunities and the risks of increasingly accessible privacy-preserving infrastructure. They do not advocate, encourage, or endorse illegal activity. The same technologies that can strengthen digital sovereignty, protect journalists, human rights organizations, researchers, and political opposition operating under censorship can also be misused by malicious actors.

The goal of this article is to encourage an open discussion about the consequences of making powerful decentralized infrastructure available to a much broader audience. As with encryption, Linux, Git, peer-to-peer networks, and the Internet itself, technological progress creates both new freedoms and new responsibilities.

Please read this article critically, verify important claims independently, and view it as a starting point for discussion rather than a definitive statement on the future of decentralized infrastructure.

Technology is neutral.

Whether it empowers democratic resistance or enables organized crime depends on the people using it.

With native Tor integration, Infinito.Nexus has the potential to fundamentally change how self-hosted infrastructure is deployed. It could become possible for anyone to create a completely private digital ecosystem with only minimal technical knowledge.

That prospect is both exciting — and concerning.

A World Beyond Traditional Surveillance

Today’s Internet relies heavily on centralized infrastructure.

Governments can subpoena cloud providers.

Internet Service Providers can monitor traffic.

Hosting companies know where servers are located.

DNS providers can suspend domains.

Payment providers can freeze accounts.

Social media platforms can remove communities.

Tor changes that equation.

By integrating Tor directly into the infrastructure layer instead of treating it as an optional add-on, organizations could operate entirely within Onion Services.

No public IP addresses.

No public DNS.

No visible server locations.

No conventional attack surface.

Infrastructure that was previously easy to discover suddenly becomes practically invisible to anyone outside the Tor network.

From Old Smartphones to Invisible Infrastructure

Perhaps the most disruptive consequence of native Tor support is that almost anyone could become an anonymous infrastructure operator.

Instead of renting a VPS or purchasing expensive server hardware, users could simply take an old smartphone, install a Linux distribution such as Droidian, deploy Infinito.Nexus, and immediately have a functional server reachable exclusively through Tor.

Modern smartphones already contain everything traditionally required for a small server:

• multicore ARM processors
• flash storage
• Wi-Fi and LTE connectivity
• extremely low power consumption
• integrated batteries acting as an Uninterruptible Power Supply (UPS)

Unlike conventional servers, smartphones can continue operating during short power outages without requiring any additional hardware.

Because all communication occurs through Onion Services, the physical location of the device becomes significantly harder to determine than traditionally hosted infrastructure.

A server could operate from:

• an apartment
• an office
• a vehicle
• a backpack
• a cabin
• virtually anywhere with Internet access

Instead of racks in a datacenter, entire organizations could operate from inexpensive commodity hardware.

Infrastructure that once required thousands of dollars could eventually fit inside a jacket pocket.

Organization Beyond Censorship

Perhaps the most transformative consequence of native Tor support is not anonymity itself — it is organization.

Modern democratic movements require far more than encrypted messaging. They need complete digital infrastructure.

Imagine a group deploying the following services exclusively as Onion Services:

• Matrix for encrypted communication
• Nextcloud for document sharing
• OpenProject for task management
• Git for software development
• Wiki systems for documentation
• forums for public discussion
• video conferencing
• identity management with single sign-on

Every service is accessible only through Tor.

There are no public IP addresses.

There are no publicly reachable domains.

There is no central cloud provider that can simply terminate the infrastructure.

For political opposition movements operating under authoritarian governments, this could fundamentally change what is possible.

In countries such as Russia or Iran, governments have repeatedly attempted to restrict independent media, block communication platforms, and pressure hosting providers into taking services offline. A decentralized infrastructure based on Tor Onion Services makes these traditional forms of censorship considerably more difficult.

If one server disappears, another can be brought online using the same deployment automation and cryptographic identities.

Instead of relying on a single datacenter, an organization could distribute its infrastructure across many independently operated devices, including repurposed smartphones running Linux distributions such as Droidian. Every device becomes part of the organization’s digital backbone while remaining reachable only through the Tor network.

This significantly lowers the barrier to building resilient communication networks for journalists, NGOs, researchers, humanitarian organizations, and democratic opposition movements.

Building Invisible Organizations

Imagine an organization deploying:

• Identity Management
• Matrix
• Nextcloud
• Git
• Email
• Video Conferencing
• Project Management
• Forums
• Social Networks
• AI Infrastructure

Every service exists exclusively as an Onion Service.

Employees connect only through Tor.

No public domains.

No public IP addresses.

No externally visible services.

From the perspective of the public Internet, the organization barely exists.

A Powerful Tool for Democracy

For many people around the world, this would be an extraordinary step toward digital sovereignty.

Political opposition operating under authoritarian governments often faces:

• Internet censorship
• mass surveillance
• infrastructure seizures
• domain confiscation
• ISP monitoring
• targeted cyber attacks

A hidden smartphone consuming only a few watts of electricity could host secure communications for an activist movement.

Journalists could publish anonymously.

NGOs could coordinate without relying on commercial cloud providers.

Entire communities could communicate through infrastructure that is extremely difficult to discover or disable.

History repeatedly demonstrates that secure communication is one of the foundations of democratic resistance.

The Other Side of the Coin

Unfortunately, technology does not distinguish between good and bad actors.

The exact same infrastructure could also be deployed by:

• organized cybercrime
• ransomware groups
• illegal marketplaces
• extremist organizations
• terrorist networks
• large-scale fraud operations
• illegal trafficking

If deploying anonymous infrastructure becomes as simple as flashing Linux onto an old smartphone and clicking through an installation wizard, the barrier to entry changes dramatically.

What once required experienced Linux administrators could eventually become accessible to almost anyone.

A hidden smartphone server could host:

• a secure school collaboration platform

or

• an anonymous criminal marketplace.

Technically, there may be little difference.

The software cannot distinguish between them.

Risks for Democratic Societies

For democratic societies such as Germany, this presents a difficult challenge.

Security agencies often rely on information obtained from hosting providers, cloud operators, domain registries, DNS providers, or centralized communication platforms during investigations.

Infrastructure that exists exclusively as Tor Onion Services reduces the availability of these traditional investigative paths.

This can make investigations more difficult and more resource-intensive, especially when organizations are technically competent and operate their own infrastructure.

A terrorist cell, extremist group, or organized criminal network could theoretically operate:

• private Matrix servers
• encrypted file storage
• internal forums
• planning boards
• identity systems
• software repositories
• anonymous web services

all without relying on public-facing infrastructure.

That does not mean such groups become impossible to detect.

Tor does not make people invisible.

Law enforcement can still use endpoint forensics, undercover operations, financial investigations, human intelligence, surveillance of physical logistics, and mistakes made by suspects.

But the balance changes.

The stronger privacy technologies become, the harder traditional bulk surveillance and provider-based investigations become.

This is exactly why the same tools that protect dissidents in authoritarian states can also create serious challenges for law enforcement in democratic states.

The Democratization of Anonymous Infrastructure

Historically, operating Onion Services required substantial expertise.

Administrators needed to understand:

• Linux
• networking
• reverse proxies
• DNS
• Tor
• certificates
• firewalls
• application integration

Automation changes everything.

Eventually, the entire deployment process could become:

1. Install Droidian on an old smartphone.
2. Install Infinito.Nexus.
3. Select the desired applications.
4. Enable Tor support.
5. Click Deploy.

Minutes later, an entire private infrastructure could be online.

No cloud provider.

No VPS.

No static IP.

No public DNS.

Infrastructure that previously required experienced system administrators becomes accessible to ordinary users.

That democratization is both empowering and dangerous.

Open Source Has Always Faced This Dilemma

This is not a new ethical problem.

Encryption protects:

• journalists
• dissidents
• criminals

VPNs protect:

• activists
• ransomware operators

Git is used to build:

• medical software
• malware

Linux powers:

• hospitals
• botnets

Artificial Intelligence can:

• accelerate scientific discovery
• generate phishing campaigns

Technology itself has no morality.

People do.

Infinito.Nexus Is Infrastructure

Infinito.Nexus is not being developed to create hidden criminal networks.

Its purpose is to simplify the deployment of sovereign, self-hosted infrastructure.

Native Tor support simply extends that philosophy.

The software itself does not decide who uses it.

The responsibility remains with those who deploy it.

The Ethical Challenge

Should powerful privacy technologies be withheld because they could be abused?

Or should society accept that technologies capable of protecting freedom will inevitably also be exploited by malicious actors?

There is no perfect answer.

Throughout history, almost every revolutionary communication technology — from the printing press to encrypted messaging — has been used for both constructive and destructive purposes.

Tor is no different.

Neither is Infinito.Nexus.

Technical Design

Native Tor support is currently being designed as a core networking feature of Infinito.Nexus.

Instead of treating Tor as an optional add-on, every deployed application can automatically receive its own Onion Service while remaining fully integrated into the deployment framework.

The current design proposal is publicly available:

Native Tor Support Requirements
https://github.com/kevinveenbirkenbach/infinito-nexus-core/blob/feature/svc-net-tor/docs/requirements/031-svc-net-tor-onion.md

Related projects:

Infinito.Nexus Core
https://github.com/kevinveenbirkenbach/infinito-nexus-core

Hetzner Arch LUKS
https://github.com/kevinveenbirkenbach/hetzner-arch-luks

Linux Image Manager
https://github.com/kevinveenbirkenbach/linux-image-manager

These projects together lay the groundwork for a future where deploying fully encrypted, self-hosted, Tor-native infrastructure becomes almost as simple as installing a mobile app.

Conclusion

Native Tor support has the potential to fundamentally reshape how self-hosted infrastructure is deployed.

For the first time, individuals, NGOs, journalists, companies, and political opposition movements could build private digital ecosystems with remarkably little technical expertise.

At the same time, the same technology could lower the barrier for anonymous criminal infrastructure.

A discarded smartphone running Linux could become a resilient, battery-backed server hidden almost anywhere.

That reality is both inspiring and unsettling.

Like encryption, Linux, Git, VPNs, and the Internet itself, Infinito.Nexus is infrastructure.

Infrastructure does not decide how it is used.

People do.

The challenge for society is therefore not whether such technology should exist, but how we choose to live in a world where powerful privacy tools become accessible to everyone.

WHERE OTHERS LOSE CONTROL – WE STAY IN THE LOOP.

https://blog.infinito.nexus/blog/2026/06/16/where-others-lose-control-we-stay-in-the-loop/

WHERE OTHERS LOSE CONTROL – WE STAY IN THE LOOP.

https://blog.infinito.nexus/blog/2026/06/16/where-others-lose-control-we-stay-in-the-loop/

I need to vent.

I don’t want to know how much time I spend singing in / logging in to some software. The employee side is just annoying - they use a #singleSignOn app, but I have to confirm multiple times every day. At least it is all accessible without removing the phone from the dock. But my customer resets their virtual desktops every night and has turned off #SSO.

I need to vent.

I don’t want to know how much time I spend singing in / logging in to some software. The employee side is just annoying - they use a #singleSignOn app, but I have to confirm multiple times every day. At least it is all accessible without removing the phone from the dock. But my customer resets their virtual desktops every night and has turned off #SSO.

I need to vent.

I don’t want to know how much time I spend singing in / logging in to some software. The employee side is just annoying - they use a #singleSignOn app, but I have to confirm multiple times every day. At least it is all accessible without removing the phone from the dock. But my customer resets their virtual desktops every night and has turned off #SSO.

I need to vent.

I don’t want to know how much time I spend singing in / logging in to some software. The employee side is just annoying - they use a #singleSignOn app, but I have to confirm multiple times every day. At least it is all accessible without removing the phone from the dock. But my customer resets their virtual desktops every night and has turned off #SSO.

Digitale Souveränität jetzt sichern

https://blog.infinito.nexus/blog/2026/04/11/digitale-souveranitat-jetzt-sichern/

Digitale Souveränität jetzt sichern

https://blog.infinito.nexus/blog/2026/04/11/digitale-souveranitat-jetzt-sichern/

Digitale Souveränität jetzt sichern

https://blog.infinito.nexus/blog/2026/04/11/digitale-souveranitat-jetzt-sichern/

Digitale Souveränität jetzt sichern

https://blog.infinito.nexus/blog/2026/04/11/digitale-souveranitat-jetzt-sichern/

Dag 3 i resan mot digital självständighet: Dags att gallra bland kontona

https://www.godaliv.se/digital-suveranitet/dag-3-i-resan-mot-digital-sjalvstandighet-dags-att-gallra-bland-kontona/

Dag 3 i resan mot digital självständighet: Dags att gallra bland kontona

https://www.godaliv.se/digital-suveranitet/dag-3-i-resan-mot-digital-sjalvstandighet-dags-att-gallra-bland-kontona/

Dag 3 i resan mot digital självständighet: Dags att gallra bland kontona

https://www.godaliv.se/digital-suveranitet/dag-3-i-resan-mot-digital-sjalvstandighet-dags-att-gallra-bland-kontona/

Dag 3 i resan mot digital självständighet: Dags att gallra bland kontona

https://www.godaliv.se/digital-suveranitet/dag-3-i-resan-mot-digital-sjalvstandighet-dags-att-gallra-bland-kontona/

Infinito.Nexus vs. YunoHost

https://blog.infinito.nexus/blog/2026/02/23/infinito-nexus-vs-yunohost/

Infinito.Nexus vs. YunoHost

https://blog.infinito.nexus/blog/2026/02/23/infinito-nexus-vs-yunohost/

Infinito.Nexus vs. YunoHost

https://blog.infinito.nexus/blog/2026/02/23/infinito-nexus-vs-yunohost/

Infinito.Nexus vs. YunoHost

https://blog.infinito.nexus/blog/2026/02/23/infinito-nexus-vs-yunohost/

Infinito.Nexus vs. YunoHost

https://blog.infinito.nexus/blog/2026/02/23/infinito-nexus-vs-yunohost/

Guten Morgen, ich hoffe, Eure Anreise nach Bremen zum #univentionsummit wird nicht zu abenteuerlich bei dem Wetter!

Hier ein kleine Reiselektüre für die, die schon mal spicken möchten, was diese Authentication Flows sind, über die ich morgen spreche:

https://www.keycloak.org/docs/latest/server_admin/index.html#_authentication-flows

#keycloak #sso #singlesignon #freesoftware @univention

Guten Morgen, ich hoffe, Eure Anreise nach Bremen zum #univentionsummit wird nicht zu abenteuerlich bei dem Wetter!

Hier ein kleine Reiselektüre für die, die schon mal spicken möchten, was diese Authentication Flows sind, über die ich morgen spreche:

https://www.keycloak.org/docs/latest/server_admin/index.html#_authentication-flows

#keycloak #sso #singlesignon #freesoftware @univention

Guten Morgen, ich hoffe, Eure Anreise nach Bremen zum #univentionsummit wird nicht zu abenteuerlich bei dem Wetter!

Hier ein kleine Reiselektüre für die, die schon mal spicken möchten, was diese Authentication Flows sind, über die ich morgen spreche:

https://www.keycloak.org/docs/latest/server_admin/index.html#_authentication-flows

#keycloak #sso #singlesignon #freesoftware @univention

Guten Morgen, ich hoffe, Eure Anreise nach Bremen zum #univentionsummit wird nicht zu abenteuerlich bei dem Wetter!

Hier ein kleine Reiselektüre für die, die schon mal spicken möchten, was diese Authentication Flows sind, über die ich morgen spreche:

https://www.keycloak.org/docs/latest/server_admin/index.html#_authentication-flows

#keycloak #sso #singlesignon #freesoftware @univention

Guten Morgen, ich hoffe, Eure Anreise nach Bremen zum #univentionsummit wird nicht zu abenteuerlich bei dem Wetter!

Hier ein kleine Reiselektüre für die, die schon mal spicken möchten, was diese Authentication Flows sind, über die ich morgen spreche:

https://www.keycloak.org/docs/latest/server_admin/index.html#_authentication-flows

#keycloak #sso #singlesignon #freesoftware @univention

Single Sign on for Furries

https://cendyne.dev/posts/2025-08-15-single-sign-on-for-furries.html

#HackerNews #SingleSignOn #Furries #TechInnovation #SecurityOnline #Community

Single Sign on for Furries

https://cendyne.dev/posts/2025-08-15-single-sign-on-for-furries.html

#HackerNews #SingleSignOn #Furries #TechInnovation #SecurityOnline #Community

Single Sign on for Furries

https://cendyne.dev/posts/2025-08-15-single-sign-on-for-furries.html

#HackerNews #SingleSignOn #Furries #TechInnovation #SecurityOnline #Community

Single Sign on for Furries

https://cendyne.dev/posts/2025-08-15-single-sign-on-for-furries.html

#HackerNews #SingleSignOn #Furries #TechInnovation #SecurityOnline #Community

Single Sign on for Furries

https://cendyne.dev/posts/2025-08-15-single-sign-on-for-furries.html

#HackerNews #SingleSignOn #Furries #TechInnovation #SecurityOnline #Community

💪 Ready to simplify DNS access for your organization? Managing DNS access across multiple domains and teams can get messy. This video shows how to use Microsoft Entra SSO with DNSimple so your team sign in once & gets the right level of access.
👉 Watch https://youtu.be/hpBNoXc2reU

#MicrosoftEntra #EntraID #EntraSSO #SingleSignOn #SSO #Security #DNS

💪 Ready to simplify DNS access for your organization? Managing DNS access across multiple domains and teams can get messy. This video shows how to use Microsoft Entra SSO with DNSimple so your team sign in once & gets the right level of access.
👉 Watch https://youtu.be/hpBNoXc2reU

#MicrosoftEntra #EntraID #EntraSSO #SingleSignOn #SSO #Security #DNS

💪 Ready to simplify DNS access for your organization? Managing DNS access across multiple domains and teams can get messy. This video shows how to use Microsoft Entra SSO with DNSimple so your team sign in once & gets the right level of access.
👉 Watch https://youtu.be/hpBNoXc2reU

#MicrosoftEntra #EntraID #EntraSSO #SingleSignOn #SSO #Security #DNS

💪 Ready to simplify DNS access for your organization? Managing DNS access across multiple domains and teams can get messy. This video shows how to use Microsoft Entra SSO with DNSimple so your team sign in once & gets the right level of access.
👉 Watch https://youtu.be/hpBNoXc2reU

#MicrosoftEntra #EntraID #EntraSSO #SingleSignOn #SSO #Security #DNS

💪 Ready to simplify DNS access for your organization? Managing DNS access across multiple domains and teams can get messy. This video shows how to use Microsoft Entra SSO with DNSimple so your team sign in once & gets the right level of access.
👉 Watch https://youtu.be/hpBNoXc2reU

#MicrosoftEntra #EntraID #EntraSSO #SingleSignOn #SSO #Security #DNS

If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

If you contribute to @wikipedia @wikidata #WikimediaCommons #Wikivoyage, you can join OpenHistoricalMap in just a few clicks, without having to juggle yet another password for yet another wiki. It works a lot like our existing OpenStreetMap login support.

#SingleSignOn #OAuth2

Allmählich kehrt im Büro Ruhe ein. 🎅🏻 Hier bin ich bei meinen Vortragsvorbereitungen für den Univention-Summit: "Authentication Flows in Keycloak". Seid Ihr dabei? 28./29.1. in Bremen.

#singlesignon #keycloak #univentionsummit #bremen #freesoftware #opensource

Allmählich kehrt im Büro Ruhe ein. 🎅🏻 Hier bin ich bei meinen Vortragsvorbereitungen für den Univention-Summit: "Authentication Flows in Keycloak". Seid Ihr dabei? 28./29.1. in Bremen.

#singlesignon #keycloak #univentionsummit #bremen #freesoftware #opensource

Allmählich kehrt im Büro Ruhe ein. 🎅🏻 Hier bin ich bei meinen Vortragsvorbereitungen für den Univention-Summit: "Authentication Flows in Keycloak". Seid Ihr dabei? 28./29.1. in Bremen.

#singlesignon #keycloak #univentionsummit #bremen #freesoftware #opensource

Allmählich kehrt im Büro Ruhe ein. 🎅🏻 Hier bin ich bei meinen Vortragsvorbereitungen für den Univention-Summit: "Authentication Flows in Keycloak". Seid Ihr dabei? 28./29.1. in Bremen.

#singlesignon #keycloak #univentionsummit #bremen #freesoftware #opensource

Allmählich kehrt im Büro Ruhe ein. 🎅🏻 Hier bin ich bei meinen Vortragsvorbereitungen für den Univention-Summit: "Authentication Flows in Keycloak". Seid Ihr dabei? 28./29.1. in Bremen.

#singlesignon #keycloak #univentionsummit #bremen #freesoftware #opensource

4ga Boards đã tích hợp OIDC!thrown Bản cập nhật mới này mang đến nhiều tính năng mới như chủ đề màu tối gây cảm hứng từ GitHub, nhật ký hoạt động, xuất 部分, cải thiện PWA và nhiều điều chỉnh chất lượng cuộc sống hơn nữa. Cộng đồng có thể đóng góp ý tưởng và phản hồi để phát triển dự án. Cảm ơn tất cả đóng góp! #4gaBoards #OIDC #SingleSignOn #Selfhosted #ProjectManagement #QUẢN_LÍ_DỰ_ÁN #XÁC_THỰC_erotisk

https://www.reddit.com/r/selfhosted/comments/1oofrww/4ga_boards_now_with_oidc_integration/

Ein Stack, der zusammenarbeitet: Warum Infinito.Nexus mehr ist als SaaS

https://blog.infinito.nexus/blog/2025/10/28/ein-stack-der-zusammenarbeitet-warum-infinito-nexus-mehr-ist-als-saas/