Is there a sensible way to place Jira itself behind a Web Application Firewall (WAF) while exposing only the “service desk” through a minimal set of endpoints? Has any guide or manual been published for this?
Hello @SEBtheSaviour
Can you provide more information about the problem you are trying to solve? What exactly are you trying to expose? Do you want only the Customer Portal for Service Desk projects exposed? Do you want to allow access to APIs separate from the Portal UI?
@Trudy Claspill I’m seeing some direct referrers to /servicedesk/customer/portal/. What I need to see is whether restricting public access to main site (jira.example.com) will still allow that path to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...and yes. I think the separation API from the PortalUI is recommended in terms of integration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.