I'm trying to change postgres9 DB password.
After upgrading Jelastic platform up to 2.5.3 on my hosting provider, I can't change webadmon database password to user defined through Jelastic API.
I using com.jelastic.api.environment.Environment.resetNodePassword(String, String, String, String) method of jelastic-public-j2se 2.2 library.
All the time when I calling it, autogenerated password sends me on email, but not password defined by me.
It worked on 1.9 platform version before upgrade.
I have noticed that the difference in the version numeration is considerable, which indicates that there was done a lot of improvements, features and were successfully fixed detected issues.
I have checked Release Notes section which is states that API feature was submitted in 2.2 Jelastic version.
Referring to API docs currently this can be done by ResetNodePasswordById method.
Related
I support the backend of a project that uses djangorestframework, django-rest-auth, and django-rest-framework-jwt. The frontend of this project is supported by other people.
Recently, the owner gave me the task to migrate the project to Django3.1 and the latest versions of other used packages. When migrating, I came across the fact that the django-rest-auth project has not been developed for more than two years and it is recommended to use its fork dj-rest-auth, and for JWT it is recommended to use django-rest-framework-simplejwt.
I replaced the dependencies in accordance with the recommendations, but faced with the incompatibility of the resulting API with the previous version.
The django-rest-auth and django-rest-framework-jwt packages use the key "token" that the user's token is located on. For dj-rest-auth when using JWT, this is the key "access_token". It turns out that when one update the backend, the API authorization specification changes.
Is there any way to avoid this?
I have a number of technical users on this system which was recently upgraded to SQ 5.2. The system uses LDAP authentication for normal users. When I try to change the password for a technical user, I get this:
Password cannot be changed when external authentication is used
I've also tried deleting the user, then re-creating it with the new password. That attempt gives the same error message.
I've made sure that the affected users are listed in sonar.properties, for sonar.security.localUsers.
This is planned to be fixed in version 5.3 : https://jira.sonarsource.com/browse/SONAR-7036
With the new Codeigniter 3.0 version what authentication libraries do you use?
Flexi auth was very good and robust with great documentation for CI 2.0 but it is old and as I can see it is discontinued. Of course it does not work out of the box with CI 3.0. I have tested it and tried to migrate it to CI 3.0 but as it uses the old ci_sessions schema I have seen that it has a lot work to be made to rewrite all the code parts that use sessions. It seems to work with file sessions and some alterations on its code though.
Community auth has a CI 3.0 version but as I have seen, it has many bugs and it is nowhere near reliable at this time. I have tested it thoroughly and it cannot work properly as it has problems with its token jar system and its cookie management. Users cannot login most of the times and it is being used as a whole third-party library at Codeigniter, which personally I don't like as it has a lot of files/folders that are time consuming to be maintained. I would prefer simple CI libraries with 1-2 models like flexi-auth. Although, I wouldn't mind Community Auth's approach if it worked properly.
Tank Auth was a reliable solution in the past but not with Codeigniter 3.0 as it has many incompatibilities too. Questions about its compatibility with CI 3.0 were asked but no airplanes in the horizon so far.
DX Auth is an old authentication library and as I can see on its github repository, there are some attempts to migrate it on CI 3.0 but I haven't been able personally to test any of them.
So, has anyone successfully integrated (or migrated) any of the previous mentioned libraries on large CI 3.0 web applications? Did you write your own? Did you stick with CI 2 until further CI 3.0 development for that matter?
Update for the down votes
This post about Authentication libraries in codeigniter was very popular and helpful. I believe that posts that help the community in that way should not be closed at least not before some helpful answers. It is not discussed anywhere before and I would really like to see the opinions of more experienced developers for that.
don't let the down votes get ya down.
check out Ion Auth
https://github.com/benedmunds/CodeIgniter-Ion-Auth
take a look at the read me, you will have to rename two files for codeigniter 3. otherwise you can see that there are recent changes to the lib. the author Ben Edmunds is one of the four developers on the new codeigniter council. http://www.codeigniter.com/help/about
Please check Dnato System Login Its Simple, Fast and Lightweight auth codeigniter.
Feature:
-Add user
-Delete user
-Ban, Unban user
-Register new user sent to email token
-Forget password
-Role user level
-Edit user profile
-Gravatar user profile
-Recaptcha by Google
-And much more
Frontend
With Bootstrap Framework.
For a simple library, I use https://github.com/trafficinc/CodeIgniter-Authit (Authit). It is very simple so I can do a lot of customizations to it or just leave it be.
check this library.that is so nice.and with many features
login / logout
Login DDoS Protection
register and signup via email. (send verification code to your email)
users can send private message to other users
user group
create permissions and access control
error in other language
this library for CI2. but if you search about this, you can find lib for CI3
http://codeigniter-aauth-test.readthedocs.io
I know that this is something like a 'RTFM' question, but I can't for the life of me find solid documentation about this.
Specifically, I have a service that uses google's oauth2 REST api to authenticate users. The library I'm using (bell), recently started making calls to the /v2 version of the API endpoint. Those calls no longer seem to support approval_prompt=force in the querystring (or something along those lines, I'm no longer able to use a special route to force a new refresh token).
Realistically, all I need to do is read the documentation for what changed from v1 to v2 of the oauth2 library, or even find v2-specific information. All the documentation on developers.google.com seems to be about the v1 api.
There is no documented list of changes at present. The main changes from/auth to v2/auth, and v3/token to v4/token is that the newer versions are certified compliant with OpenID Connect. The earlier versions had a few inconsistencies with the spec, mostly because when Google launched them the spec was not yet final.
approval_prompt is now prompt. To get your approval_prompt=force behavior on the newer endpoint, specify prompt=consent. Other values for the prompt parameter are defined in section 3.1.2.1 of the spec.
Other changes, in no particular order:
the ID Token iss value is now https://accounts.google.com, was accounts.google.com
nonce is required for implicit and hybrid flows
ID tokens on the newer endpoints may contain profile claims (if the profile scope was requested), saving a call to userinfo.
I have a Unity project that I'm trying to build out to Web Player for Facebook. The project previously existed as an Android app and works well with Parse as a backend for high scores.
However, in the web player, I get an authentication pop-up titled "Authentication Required" and the message "A user name and password are being requested by https://api.parse.com. The site says: "Parse"" with Username and Password fields. Entering my Parse credentials didn't seem to work here either. I don't have a Parse User to try either - I just rely on Parse to generate them automatically without passwords. The scores never actually get loaded because this stops the process.
It works in the Editor. Has anyone had a problem similar to this? A search came up empty.
I've encountered the same message after upgrading to Unity 5 with the latest build for parse on the asset store (v. 1.3.5). While it's not a preferable solution downgrading to a previous version build (4.6) the problem does no longer occur.