AI Prompts for Diagnosing Authentication Breaks

Quote the output from the authentication function located in [FILE] at line [LINE]. Then, compare this output to the expected results outlined in the authentication requirements. Please highlight any discrepancies you find, and provide a brief explanation of their potential impact on the authentication process.

Please provide the exact error message you received during your login attempt: [ERROR MESSAGE]. Analyze this message to determine which specific authentication flow is failing. Include details about the potential causes of the error and any steps that can be taken to resolve the issue.

Please explain your understanding of the authentication flow for the use-case of BOLT-BREAKING-AUTHENTICATION. Include details about each step in the flow, such as user initiation, credential verification, session establishment, and any security measures in place. Additionally, identify any potential areas of confusion or misunderstanding you may have regarding this process. Format your response as a structured outline with clear headings for each step.

Identify the expected behavior of the authentication process when a user attempts to log in, and compare it to the actual behavior currently observed. Please provide a detailed breakdown of the steps that should occur during a successful login, including any error messages or issues that users are experiencing. Format your response in a table with two columns: one for the expected behavior and another for the actual behavior, highlighting any discrepancies.

Please analyze the authentication process for the use-case of [USE-CASE] and identify the specific rule or constraint that was violated. Provide the exact clause from the authentication requirements that was not followed, and explain the implications of this violation on the overall security of the system. Format your response as a detailed report, including recommendations for how to address the identified issues.

Please revert the function signature in the file located at [FILE] on line [LINE]. The original signature is [PASTE], and the modified signature is [PASTE]. Before applying the change, provide me with a diff of the modifications to ensure accuracy.

Rewrite the session management logic in the file [FILE] at line [LINE]. Ensure that the logic adheres to the original flow by validating the session token before granting access. Additionally, provide a brief explanation of the changes made and how they improve security and maintainability.

Please update the authentication middleware located in [FILE] at line [LINE] to ensure it properly accommodates the new feature. Clearly outline the changes made and explain how they improve the functionality of the middleware. Additionally, confirm that no other parts of the code have been altered during this process.

Please review the token format in [FILE] at line [LINE] to ensure it complies with the expected structure. If the format does not meet the requirements, correct it to match the specified format. Provide a brief explanation of the changes made and confirm that the token is now compliant.

Please verify the installation status of the authentication library in the dependencies for the project. Check if it is correctly installed and determine if it is outdated. If it is missing or outdated, provide detailed steps on how to reinstall it, including any commands or configurations needed to ensure proper functionality.

Please execute the authentication test suite for the [APPLICATION NAME] to verify that all login scenarios pass without errors. Document any failures encountered during the testing process, including the specific scenario that failed, the error messages received, and any relevant logs. Provide a summary of the overall test results, highlighting any areas that require further investigation or fixes.

Please display the differences in the authentication function changes based on the provided code snippets: [OLD_AUTH_FUNCTION] and [NEW_AUTH_FUNCTION]. Ensure that you explain how each modification aligns with the expected behavior outlined in the requirements, highlighting any improvements or issues that may arise from these changes. Format your response as a detailed report, including sections for the diff output, alignment with requirements, and potential impacts on functionality.

Replay the original failing login scenario for the bolt-breaking authentication use case to confirm that the issue has been resolved. Please document any changes in behavior compared to the previous failure, including specific error messages, response times, and any differences in user experience. Format your findings in a structured report that highlights the key differences and provides a summary of the resolution status.

Please analyze the session management system for edge cases related to [USE CASE]. Specifically, test scenarios such as session timeouts, concurrent logins from different devices, and session persistence after network interruptions. Provide a detailed report on how each edge case is handled, including any potential vulnerabilities or issues identified, and suggest improvements if necessary. Format the findings in a structured document with sections for each scenario tested.

Please verify the state of the authentication flow for the use-case of BOLT-BREAKING-AUTHENTICATION. Check the output of the login function and confirm that it matches the expected success response. Provide a detailed report that includes the actual output received, the expected output for comparison, and any discrepancies or issues identified during the verification process.

Please provide the exact session-opening constraint for the authentication flow validation in the context of [USE-CASE]. Use the following format: 'Before any authentication step: verify the token format and session validity. If any issue occurs, stop and log the error before continuing. Never proceed without validating the authentication flow.' Ensure that the output is clear and ready for direct use.

Create a documentation template for the authentication flow with the following structure. Start with a section titled 'Authentication Flow' where you describe the flow in detail as [DESCRIPTION]. Next, include a section for 'Expected Behavior' that outlines what the expected outcome should be in various scenarios as [EXPECTED OUTCOME]. Finally, add an 'Error Handling' section that specifies how errors should be managed and what the error responses will be as [ERROR RESPONSE]. Ensure the template is clear and easy to follow for future reference.

Please create a naming convention for session management functions using the format 'session_[ACTION]_[SCOPE]'. Define what types of actions should be included, such as 'create', 'destroy', or 'validate', and specify the contexts that might be relevant, like 'user', 'admin', or 'guest'. Provide a list of at least five examples following this convention, ensuring clarity in how each part of the name reflects its purpose and context.

Please create a self-check request for the authentication flow in the context of bolt-breaking authentication. The request should include specific criteria to verify before any deployment, such as ensuring that the authentication flow passes all tests, that no errors are logged in the console, and that all user scenarios are covered. Format the output as a checklist that can be easily referenced during the deployment process.

Please create a pre-deployment check for authentication libraries in the context of a bolt-breaking authentication use case. The check should verify that all authentication libraries are up to date and correctly installed before deployment. If any libraries are missing, the process should be halted. Format the output as a clear checklist that can be easily followed during the deployment process.