nextcloud / nextcloud/integration_zammad
connected accounts -> zammad integration forces https://
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 4
- Avg merge
- 15d 21h
- Merged PRs (30d)
- 1
Description
I'm testing the zammad->nextcloud integration, but i'm unable to specify the "Zammad instance address", because what every you try todo it always prefixes the address with https://.
I'm not sure if the server will use this address to connect with zammad, or if the connection would run via the browser, which for me would require to specify a different address, due to the setup in containers.
I'm not really concerned about about a secure communication at this point, because either it's container to container traffic, within the same subnet, or if it's via an browser connection, all traffic is routed through a VPN. So http:// traffic is fine.
The relevant code seems to be here; https://github.com/nextcloud/integration_zammad/blob/master/src/components/PersonalSettings.vue#L160
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in src/components/PersonalSettings.vue around line 160 and trace how the Zammad instance address is assembled and used. Confirm whether an http:// address can be entered and used for the integration, including the container or browser connection described in the issue; done means the address is no longer forcibly prefixed with https://.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100