-
Suggestion
-
Resolution: Won't Fix
-
10
-
Summary
The domain verification status is MISSING_TOKEN and when the users try to verify the domain again it shows the following message:
Which does not have any link to the status MISSING_TOKEN that is usually triggered when there is an issue to maintain/confirm the domain claim.
Steps to Reproduce
Unknown
Expected Results
Either that error should not be displayed or the status of the domain verification should be different.
Solution / Workaround
No current workaround but disregard the error message and verify the domain.
[ACCESS-629] *MISSING_TOKEN* status leading to a incorrect "Domain already verified" error
This keeps happening for some reason. I have to log in and click verify domain to fix it and stop the email warnings.
Thank you for your valuable input and comments. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish.
This suggestion is a priority for our development team, but I am not able to provide an accurate estimate for when this will be resolved. We will update this issue as soon as we can confidently project a release.
Please don't hesitate to contact me if you have any questions.
Regards,
Avni Barman
Email
Product Manager, Atlassian Access
jnunes@atlassian.com That is not an error message, but rather a warning saying you might override settings for the domain you already own. Both the warning and the status of the domain claim is accurate in this case, in the sense that
(1) the org is regarded as the owner of the domain, but the token is missing (therefore MISSING_TOKEN status, which usually suggests there something needs to be done with the client settings)
(2) if the org admin tries to do some operation at this point, he/she might override current configuration, thus the warning message. Depending on the usecase, it is up to the admins to decide to proceed or not.
I believe the way to present the message which appears to be like an error is intentional. Because in many other use cases org admins do accidentally re-verify domains they already own and regretfully reset the configs.
In the case of MISSING_TOKEN, discarding the message and just verify the domain seems to me the right way to go. With this said, we can possibly look into providing some docs to help admins understand this message better.
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!