Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce logout section for sechub webscan config to avoid logouts by the ajax crawler during scans #3923

Open
winzj opened this issue Feb 25, 2025 · 0 comments · May be fixed by #3939
Open

Comments

@winzj
Copy link
Member

winzj commented Feb 25, 2025

Siutation

Currently we do not notice when the webscan with ZAP performs a logout during the ajax crawler scan.
The regular spider and the active scan can be handled by defaults or adding excluded URLs to the webscan configuration.

Wanted

For the ajax crawler we want a specific section which specifies the logout html element.

Solution

Introduce a logout section inside the sechub webscan config. The following example might change before the implementation:

{
  "apiVersion": "1.0",
  "webScan": {
    "url": "https://example.org",
    "login": {
      "url": "https://example.org/login"
    },
    "logout": {
      "xpath": "//*[@id=\"loginButton\"]",
      "htmlElement": "button"
    }
  }
}

Important

  • the logout section is optional, but when a logout section is defined xpath and htmlElement MUST be present
@winzj winzj self-assigned this Feb 25, 2025
@winzj winzj added this to the Server 2.7.0 milestone Feb 25, 2025
@sven-dmlr sven-dmlr modified the milestones: Server 2.7.0, Server 2.8.0 Feb 26, 2025
winzj added a commit that referenced this issue Feb 27, 2025
- add logout to openapi.yaml
- add logout to sechub config model
- add validation with tests
- add example file with validation
- add documentation example
@winzj winzj linked a pull request Feb 27, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants