Introduction:

I am part of a growing number of CubeCoders' AMP users who are confronting a harsh reality: the much-advertised LDAP/SSO feature is fundamentally non-functional. My journey with AMP over the past 20 months has been consistently hampered by this unfulfilled promise. Despite exhaustive attempts using every conceivable setup - from Authentik to OpenLDAP, AD, on both Linux and Windows platforms - the promise of a working LDAP integration has remained elusive, a mere shadow of what was advertised.

But this experience isn't just my own; it's shared within the AMP user community. In my interactions with fellow users, those who have ventured into the realm of LDAP integration, the story is unanimously one of frustration and disillusionment. The singular outlier in this widespread issue is Mike, the creator of AMP, whose assertions of a functional LDAP system stand in stark contrast to the experiences of the user base.

The Core of the Problem:

This goes beyond mere technical shortcomings; it touches upon the fundamental principles of trust and honesty in business practices. CubeCoders continues to market LDAP/SSO as a key feature of AMP, blatantly disregarding the overwhelming evidence of its non-functionality. This ongoing false advertising is deceptive and shows a concerning lack of respect for us - the users who rely on AMP for important projects and workflows. It creates not only operational hindrances but also erodes the trust we place in CubeCoders and its product.

Our Collective Demand:

1. Immediate Acknowledgment: It is imperative that CubeCoders, and Mike in particular, publicly recognize and address this widespread issue.

2. Transparent Action Plan: We urge CubeCoders to provide a transparent, detailed roadmap for resolving the LDAP/SSO feature issues, complete with realistic and achievable timelines.

3. Engagement with the Community: A commitment to open, consistent communication channels is essential for providing updates and engaging in meaningful dialogue about LDAP issues.

4. Truthful Advertising: We demand that CubeCoders revises its advertising to reflect the actual capabilities of AMP, thereby restoring a measure of honesty to its marketing efforts.

5. Alternative SSO Option: If LDAP integration continues to be unworkable, we demand the addition of an alternative SSO option in AMP, such as OIDC/OAuth2, SAML, or forward auth. This would provide a viable solution for users needing reliable single sign-on functionality.

This petition is a unified call for accountability, respect, and proactive measures. Our patience has been tested and now is depleted. The time has come for CubeCoders to step up, acknowledge this pervasive issue, and implement a tangible solution.

The Impact of Your Signature:

Signing this petition is a crucial step towards initiating tangible change. Here's what we aim to achieve through our collective voice:

1. Bringing the Issue to the Forefront: With every signature, we send a clear message to CubeCoders and Mike that this issue cannot be ignored. It's about amplifying our collective voice to ensure that our concerns are heard and acknowledged.

2. Creating Accountability: This petition is a tool for holding CubeCoders accountable. It's a public, tangible record of the number of users affected by and dissatisfied with the current state of LDAP in AMP.

3. Fostering Community Solidarity: By signing, you join a community of users who share your concerns. This solidarity is powerful – it shows that we're united in our demand for a solution.

4. Direct Engagement with CubeCoders: The signatures will be presented to Mike and the CubeCoders team as a formal expression of the user base's dissatisfaction. 

5. Driving Immediate Action: The ultimate goal is to catalyze immediate action from CubeCoders. With a significant number of signatures, we can push for a faster response and resolution to the LDAP issue.