I seem to have run afoul of a known bug with RESTfulServer: https://github.com/silverstripe/silverstripe-restfulserver/issues/6
I'm using SilverStripe 3.1 with RESTfulServer. On my test server, the setup functions as expected: when not logged in, a request to http://www.example.com/api/v1/ObjectName/ID pops up a basic HTML auth box, and a username and passw## Heading ##ord can be entered successfully.
The test server is running Ubuntu 14.04 with Apache2, PHP5 and MySQL5 from the repos.
On the production server, when an unauthenticated user tries to GET http://www.example.com/api/v1/ObjectName/ID the same basic HTML auth box pops up, but the login always fails.
The production server is hosted at icdsoft, running PHP5, MySQL5 and Apache2.
Things I've tried:
- Including the credentials in the URL: http://user:pass#example.com/api/v1/ObjectName/ID
- Removing special characters from the login name and password
- Calling http://www.example.com/dev/build?flush=1
If anyone could shed some light on a cause or solution, I'd be very grateful.
Thanks,
Jeremy.
Related
I'm trying to connect to Snowflake using SSO. I am running the following script (from here):
import snowflake.connector
ctx = snowflake.connector.connect(
user='<username>',
account='<accountname>',
authenticator='externalbrowser'
)
cs = ctx.cursor()
try:
cs.execute("SELECT current_version()")
one = cs.fetchone()
print(one[0])
finally:
cs.close()
The only change I have made is passing the authenticator='externalbrowser' argument (see this) to the connect method instead of password. (user and account cannot be left blank so I'm just putting in dummy strings).
After running the script it displays the following message but a browser tab never appears:
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...
Not sure if this is relevant, but if I leave it for a few minutes, the script ends with the following error:
snowflake.connector.network.RetryRequest: HTTP 403: Forbidden
I have seen similar questions, but not an answer that would resolve the issue yet.
That <username> likely should be an email address. See https://community.snowflake.com or https://docs.snowflake.com/en/user-guide/admin-security-fed-auth-use.html#setting-up-browser-based-sso
With browser-based SSO, the Snowflake-provided client (for example, the Snowflake JDBC driver) needs to be able to open the user’s web browser. For this reason, the Snowflake-provided client and the client application that uses it need to be installed on the user’s machine. Browser-based SSO does not work if the Snowflake-provided client is used by code that runs on a server.
I assume you have provided the correct user name and password. Now if you are still getting this error, make sure you access the snowflake account using the default browser (which the python program is accessing) and keep your SSO session active.
Now run your python program and it must work.
there is nothing much required and your code parameters looks good
authenticator='externalbrowser'
I have gone through all the steps and actually logged into the boards app from
wolkenkit-boards
The app starts fine and I can login but the page keeps refreshing at http://local.wolkenkit.io:8080
Has anyone same had the same experience ?
I found out that the docker containers had to be restarted by running
npx wolkenkit start
again and then and only then running the frontend. Otherwise if the certificate is added after the backend is already running the backend sees no authentication and the frontend does so it keeps re-rendering.
I have a meteor app that is using the email and passwords packages to handle basic password reset functionality.
On my local machine I set the MAIL_URL env variable to:
smtps://{user}:{password}#smtp.gmail.com:465
and after some fiddling with the associated gmail account (I had to allow less secure applications) it worked.
My live environment is heroku, so I set the env variable there using:
heroku config:set MAIL_URL=smtps://{user}:{password}#smtp.gmail.com:465
and then confirmed that it was set using heroku config. But for some reason when I try to reset the password on my production environment, it throws the following error:
Exception while invoking method 'forgotPassword' Error: Invalid login:
534-5.7.14
I even did a heroku restart to be absolutely sure that the env variable was picked up and I still get the error. What's odd is that this is the same error I was getting before I enabled "Less secure apps".
Can anyone see why this might happen? Suggestions as to how I might fix it?
in the Heroku web on your box in Settings/ Config Vars do you actually see this setting?
I see your issue may be due to not confirming the Captcha... Check this out: Nodemailer with Gmail and NodeJS
I have terrible issue with Webtop 6.7 SP1 P12 (I have tried also testing P26) with SSO (kerberos) login into Webtop application.
On the user enviroment Web browser is in version IE 8.0.7601.17514 and operation system is Windows 7.
When I login into application (SSO authentication is succesful) result screen is missing some frame:
Sometimes frames are not behaving like this:
in this case URL is also strangely modified (part of it was deleted).
Java (1.6.0.27) is installed correctly. I also checked security setttings on JAVA and IE, but I don't see any incorrect parameters here.
When I use web browser Firefox 3.5.19 to login into the Webtop (SSO is active too) GUI is loaded correctly with frames..
My another test was under operation system Windows XP, IE 8.0.6001.18702. The Webtop GUI workiing correctly.
When I tried logging into Webtop instead of the hostname by use IP address application server, GUI working correctly. In this case SSO is off.
I tried change verzion JAVA vs IE but nothing helps.
Wireshark network protocol analyze capture this HTTP issue:
this problem occurs on 6 users of total 100.
Please, do you have any ideas for me?
Thank you so much.
Lukas
Investigating further we found that non-working users were part of 100+ AD groups resulting in a large kerberos token size.
I changed tomcat config file "server.xml" to increase http header limit to "maxHttpHeaderSize="16384"".
<Connector port="8080" maxHttpHeaderSize="16384" protocol="HTTP/1.1" ... />
Here is the link to fix:
http://blogs.adobe.com/livecycle/2012/08/avoiding-livecycle-kerberos-based-sso-problems-for-active-directory-users-with-large-group-memberships.html
I have been using Squirrelmail version 1.4.22 for over 2 months now and its been working perfectly.
Suddenly this morning users cant login and it gives them this error:
ERROR
You must be logged in to access this page.
Go to the login page
When i use an alternative mail client users are able to login into the mail accounts fine. I have tried to read online and even reinstall squirrelmail but still brings the same error and even within this forum and everybody seems to point it to a cookie issue. I have cross-checked by cookie session settings both on the server and browser and i don't seem to see an issue.
Please advise will be grateful for any help
Create php file in httpdocs of your web site with code:
<? phpinfo();
Check for value of session.save_path variable
Check for permissions on folder which defined in session.save_path:
ls -ld /path-to-folder
it should be 1733
Also check for errors in log file in
/var/www/vhosts/<your domain name>/statistics/logs/error_log