Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I keep receiving authentication error when syncing Jira directory 403 forbidden error Edited

At the moment I have established application link between bamboo and  Jira through the apache proxy. There is literally no mismatch between the application name mentioned in Jira and the application name i input in bamboo to establish a connection.  i have provided my public ip in my application name within JIRA and create a password as well and still getting the same error. I need to know if there is something else im missing. i even recreated the Bamboo application name and password several times on JIRA. only right clicking and pasting username and password on both ends therefore there should be no typing errors. Also im using amazon elastic ip therefore my public ip never changes even after server restart. 

Network im dealing with 

First server has:                           Second Server:

EC2                                             local

Bamboo                                      JIRA

Apache proxy                             Second Proxy

 

both proxy have been configured with proxy name proxy port and scheme respectively

 

Connection test failed. Response from the server:
com.atlassian.crowd.exception.ApplicationPermissionException: Forbidden (403) Encountered a "403 - Forbidden" error while loading this page. client.forbidden.exception Go to Jira home

1 answer

1 accepted

Solved it there was private ip issue. I had to put in the bamboo public ip and the proxy private ip  in the application name and password section in jira. This is because jira could not recognize the internal proxy ip as a request coming in from bamboo server. This error was because i only stated  public of bamboo in the settings.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Confluence

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

335 views 23 8
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you