I have nginx-unit server.
I don't use nginx, because my application is fully dynamic and test purpose products.
However it doesn't have basic authentication like apache.
Is there any alternative to basic authentication on nginx-unit ??
I should use nginx?? if so, is there any alternativce to basic authentication??
If I'm not wrong kerberos authentication works well if you don't want to use basic auth and your use case applies. You can use sssd with Samba to make it work.
If you are looking something simple (like checking name-values in URI) for authentication than you can try to use matching in routing.
Related
I am using a axis camera which is served by apache2, the authentication mechanism is apache basic auth. Ssl is configured for the domain. The problem is that I cannot call an api for streaming using the embedded url for example:-
https://user:pass#sub.domain.com/axis-cgi/mjpg/video.cgi
This is no longer supported by google as per this post and blocked by chrome.
https://www.chromestatus.com/feature/5669008342777856
I tried by passing the credentials along with the url and it is also not working.
https://sub.domain.com/axis-cgi/mjpg/video.cgi?user=user&pwd=pass
This camera is running in a linux customer OS, is it possible to setup an alternative authentication which supports my needs. Furthermore is it possible to by any other means?
Thanks
you may try
https://user:pass#sub.domain.com/axis-cgi/mjpg/video.cgi
good luck
this is to add enough flesh to this post.
How would I go about deploying a web app intended for only a single user (myself)? I feel like making a login that only accepts 1 user is the wrong method and also easy to hack? Would it be a good idea to make it only accessible from a certain IP? Please advise! Thank you. Backend will be using nodejs.
If I were you, I would program the back-end the proper way. This involves generalizing the entire implementation so that any hypothetical user with the correct password could use your login system. You could still authorize and authenticate the application so that when anybody else tries to log in, you automatically decline their request. If you are concerned about security, ensure that you are using SSL, basic encryption, hash passwords and, most importantly, do not use your own authorization library. It is far more secure if you use OAuth instead of using an IP, for example. Last, but definitely not least, make it as hard as you can for hackers to steal your data in the client side. This way, you also learn a lot of things that might come in handy in the near future.
I was trying to implement some sort of security in an node.js rest api, either using tokens, avoiding oauth, which is the easiest option?
Thanks!
Have you looked at passport http bear? This would allow you to secure your api end points.
You can look into http://passportjs.org/ This is the lib I often see when looking at examples.
Which Node Framework are you using? Have you looked at https://www.npmjs.org/package/iron for tokens Authorization and/or Bell for Authentication https://www.npmjs.org/package/bell ?
HornetQs default SecurityManager (HornetQSecurityManagerImpl) will check users/roles that are stored in the hornetq-users.xml. I want use LDAP for authenticating users; I have two ways:
Using Jass, and use it with LDAP for authenticating users.
Implementing SecurityManager interface manualy, and using LDAP in my own security manager implementation.
Which one is better? Other approaches? What should i do? (experience, sample)
I'd say it's always better to use something that's ready and tested. Using JAAS with Ldap will give you an easier path as that should work nicely.
On the hornetq's distribution there's an example showing how to configure JAAS. You can just get the distribution zip at http://www.jboss.org/hornetq/downloads.html and refer the the examples that are part of hornetq already.
I posted a variation of this question to the CouchDB user list and haven't received a response yet.
I'm curious to know if anyone else has built a so-called "CouchApp"; a pure HTML/JavaScript application hosted directly within CouchDB. If so, how did you handle user authentication? I'd like to be able to create a typical login form (username, password) and then use those credentials either against a view or some other mechanism before passing the user along to the application (while storing their (encrypted) user ID in a cookie, presumably).
I'm used to simply proxying through something like couchdb-python and a normal web server, but would like to know any best practices with respect to authenticating users in these kinds of CouchApps.
Edit: A year later, and this is now built into CouchDB. This video is a great demonstration. (Thanks Daniel!)
CouchDB has released a simple authentication api but has no in built authentication mechanisms as of yet. The simplest and easiest way to do this is to use an http proxy for authentication. However this has limitations on how much you can restrict access on a per document basis. When CouchDB gets some more support for built-in authentication modules then it should be easier.
If you want to try your hand at coding an authentication module then you can check out the source for the javascript security_validation tests in this file:
http://svn.apache.org/repos/asf/couchdb/trunk/share/www/script/couch_tests.js
and the default_authentication_handler in this file here:
http://svn.apache.org/repos/asf/couchdb/trunk/src/couchdb/couch_httpd.erl
that would get you started anyway.
This question has been around for a while (1.5 years!) and things have matured quite a bit since it was answered. Watch the video above, but it doesn't explain how to build it into your app. It looks like most of the answers are now found here: Security Features Overview and at the end of this document: CouchDB Security.