Bugzilla, no login required to view bugs - ubuntu-16.04

Bugzilla has to have a way to stop anyone random person to view the bugs, but I can't find it. This question is similar to How to prevent anonymous (users that are not logged in) BugZilla access? but there is no answer to the question.
To elaborate further, as of right now, anyone can access my bugzilla server, and click on the Browse button to view any bugs we have listed. I've searched through all the administrative settings, and I can't find a way to disallow this. Surely it exists. Any help would be appreciated.
using Bugzilla 5.0.3

Go to Administration page, select User Authentication and then find the option "requirelogin".
Make sure it is checked as "ON"

Related

Enforce HTTPS not available on GitHub

I was able to have HTTPS but just recently I cannot create an HTTPS website. Is there anyone familiar with Namecheap and GitHub Pages that has either overcome the issue or can help?
Namecheap
GitHub Pages
CNAME
404.html
index.html
Thanks to #VadimKovrizhkin for asking. Yes, I do remember now.
Step 1
(I did not try this, but it is definetely related to the problem)
Try disabling all extensions. If the checkbox is enabled, re-enable all extensions one-by-one to see which one it is. If you find which one it is, you may not need to permanently disable it.
The extension may have settings/preferences. For example, mine was an ad-blocker. I went to its preferences in my browser settings. Then, I disabled it on the specific site I wanted.
I have not tried this out on this problem though.
Step 2
If that did not work, here's what helped me enable the checkbox.
This step is very simple.
Go to the "Pages" section (or wherever the checkbox is)
Lay your cursor over the checkbox.
Right click, "Inspect Element", and go to the element manually if it doesn't automatically.
Find the attribute on the <input type="checkbox"> element called disabled.
Completely delete that attribute from the element.
The checkbox should be enabled again.
The reason it may not be working
It looks like this issue has not been fixed yet.
I can tell because I ran into this problem a few days ago setting my domain.
I did the inspect element trick and it works great.
The reason it may be doing this is browser support, or an extension(s) that may be breaking the site.
Other GitHub users have had browser support issues on Firefox and Chrome (maybe other browser too).

Tableau Personal Space 401 on Web Edit

We recently upgraded to the latest version of Tableau and are encountering a serious problem. No-one in the tableau community has answered the question and even our paid Tableau support is not responding to us!
We are embedding a viz in our site and then allowing users to click on the "Edit" button which opens up a web-edit version of the workbook. We have special permissions setup that allows them to even save their changes. This has all been working fine.
As of the most recent upgrades where Tableau introduced this idea of a Personal Space we now get a 401 when trying to save in the Web Edit (now labelled "Publish as")
Clicking "Publish As" loads a modal which is meant to display a list of locations to save to but instead displays a spinner which never goes away. The console indicates an error specifically wit the new personal space - 401 - No authentication credentials were provided.
We are using trusted ticket authentication to display our embedded vizzes and have had no problems with web edit saving until now. If we log directly into Tableau the web edit saves perfectly. So it seems to be an issue of Web Edit Saving + Trusted authentication, specifically as it relates to personal spaces.
Seems clear to me that this is a Tableau bug but wondering if anyone can suggest any kind of fix or workaround.
Thank you
This has been confirmed by Tableau as a bug in their latest versions. Unclear when it will be fixed.
They provided us with the following workaround (which is not ideal from a security perspective) but works.
Workaround provided by Tableau. Configuration change required, setting unrestricted tickets to true.
https://kb.tableau.com/articles/issue/login-prompt-when-embedding-server
This is a temporary measure while Tableau develops a more permanent solution.

Could not access to the actions console of our project

We have several action console projects. But recently I could not access to one of our action console projects.
Normally I will access from list in here:
https://www.screencast.com/t/CWlbqhRFc
But now it always show error when I click to one of our projects in there.
https://www.screencast.com/t/b6DmCIcmDsec
I contact with google and ask them for helping. They said that it is caching problems and ask me clear cache on browser. I did it but error still happen. Many other members of this projects also got that error (We shared account of project with some members).
Does someone know the reason of this bug and how could I fix it?
Please check the Roles you have for the project. You need to give Viewer Role to all the members of the project who are getting this error.
Please have a look into this Stackoverflow post as well.
There are a high chance there are a problem in google server. Because after we add a new device model. We could access our project again.

Joomla 3.0 SEF URLs sending to random wrong articles

My site eighttwentydesign is running Joomla 3.0. I have SEF URLs on, and have done for sometime without issue. But today when you go to the site, and click on anything, say portfolio you get the home page under the portfolio's URL, but if you add a leading slash at the end, the right article (portfolio) shows. Additionally, if you click on say "Web Design" it sends you to the Portfolio page. I might add this menu is a menu within Joomla - not be adding internal links manually
Doesn't work: http://www.eighttwentydesign.com/portfolio
Does work: http://www.eighttwentydesign.com/portfolio/
I have checked the .htaccess, and actually reverted it to the original with no luck, I have check Global Config but I can't see anything which may cause this. It was working nicely yesterday. I haven't adapted with any PHP source or anything in the past few weeks, the only notifiable thing I have done is yesterday enabling the Cache - have others experienced problems after doing this? I have disabled it under global config, with no avail.
Exact Joomla Version is 3.0.2 with very few plugins
I do have daily backups, but would rather a solution and be able to figure out a prevention from that, rather than just putting on a band aid.
I've search for a good couple of hours, and aside from just not being able to fix it, it appears no one else is experiencing this, so I am starting to think it may be a bug.
Just as I was about to post this I discovered my solution.
If you are having your SEF URLs display the wrong content then solve it by disabling the Cache plugin. You can do this by doing the following steps
Login to Joomla backend
Navigate to Extensions > Plugins
Go to "System Cache"
Disable system cache
I hope this helps someone in the future as I really struggled to find any answers on this.

How can I give feedback on Eclipse?

How can I give feedback on Eclipse?
Here's what I've tried:
Eclipse -> Help -> Report Bug or Enhancement... takes me to a Bug window that gives me a Anonymous can not submit Tasks! error when I try to submit it. I have to spend extra time explaining that I'm not submitting a bug, but an enhancement, or rather a piece of feedback. I feel there must be something more effortless and painless than this method.
If you click the "Anonymous can not submit..." link, it will bring up a dialog to configure your connection to Eclipse bugzilla system. Since you obviously don't have an account there, use the "Create new account" link in that dialog to create an account (it dumps you to the web site to do that).
Eclipse Bugzilla is for entering bug reports or feature/enhancement requests. If what you want to say is neither of those, try posting on the Eclipse Community Forums. Also, if you would prefer to file a bug or enhancement via the standard web interface, you can access it here. It's generally a good idea to search for similar reports before posting a new one. It's also not a bad idea to discuss the topic on the forums before creating a bugzilla report.