owncloud 10.3.2 SMB shares, only one user can acces at a time - smb

I have a problem with owncloud 10.3.2. I added SMB shares to owncloud, however, only one user can acces them at any given time. All the other users that try to sign in get the following error when trying to access a folder:
Some of the configured external mount points are not connected. Please click on the red row(s) for more detail
Clicking on a red row gives:
Couldn't get the information from the Owncloud server:0
Thanks in advance!

Found the problem. When I went to my owncloud url and signed in, I got redirected to the same sign-in page, different url. Cookies were saved. Clearing cookies after the first failed log-in fixed it.

Related

How to Create OAuth Client ID?

I am trying to run this github project.
For this I need to create credentials and OAuth Client Id.
When I click to create. After selecting web applications and typing the name I see authorised javascript and authorised redirect uri.
So what should I enter there because I tried with keeping both fields empty. But I got error saying no redirect url found for client id
Please help me.
I am using Developer Console for first time can't find any help on internet. This site is my last hope.
I did as said in [comment].2
Here is what I got in Linux shell and the error i received on redirected url opened webpage.
Linux Shell Message
/YouTube-Subscription-Importer/env/lib/python3.6/site-packages/oauth2client/_helpers.py:255: UserWarning: Cannot access subscribe.py-oauth2.json: No such file or directory
warnings.warn(_MISSING_FILE_MESSAGE.format(filename))
Your browser has been opened to visit:
https://accounts.google.com/o/oauth2/auth?client_id=1069660256195-n8adm0dmi70v29i55hcfblftle09hb5n.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fyoutube&access_type=offline&response_type=code
If your browser is on a different machine then exit and re-run this
application with the command-line parameter
--noauth_local_webserver
Snipe of what redirect url webpage said
**MOST IMPORTANT
I am running this in windows bash.
Now tell me what to do next.
I just simply need a tutorial/how-to use guide for Google developer console credentials and OAuth Screen.
**
You need the redirect URL, you will be redirected from Google OAuth Consent Screen to https://REDIRECT_URL?code=AuthorizationCode, you can just set it to http://localhost.
After creation, you can your find Client ID on the Credentials page.

on click .. Suspicious link error in gmail(laravel)

When a user signs up on our website, they get an email verification link, but whenever they try to click on any link in that mail, they get the alert error message:
Suspicious link
This link leads to an untrusted site. Are you sure you want to
proceed?
We are using the sendgrid mailer system and we are certified to https.
Where is the problem coming from?
This is mostly in newsletters(Mailers), we need to verify the domain in Google
For authenticating domain using the steps below:
Go to postmaster.google.com.
On the bottom-right, click the + button.
In the box that pops up, enter your authentication domain.
Next, prove that you own the domain by adding a DNS TXT or a DNS CNAME record.
For reference: https://productforums.google.com/forum/#!topic/apps/xSV6J-Nmkmc;context-place=forum/apps
Also it happens when we have https(ssl) but we are using the link http
We were recently having this issue in our account verification emails as well. Verifying our domain through DNS records as recommended by Google was not enough.
The ultimate solution for us was ensuring that every link has an alt tag with descriptive text.
Verify!
Please check once for a DNS record. You can check it from below url
https://mxtoolbox.com/SuperTool.aspx
And also check for the DMARK record which is found in your mx records or not.
Go to sendgrid.com > Settings > Sender Authentication and configure DNS

How to get different connection for different browser session/machine so I can get different profile feeds?

I followed tutorial on:
https://spring.io/guides/gs/accessing-facebook/
I run the application and successfully authenticate with a single user. Home page returns my feeds.
Now I connect to the application from another browser/machine and go to home page - I see feeds of first browser session/machine.
I am expecting to be asked to log in again when connecting from different browser/machine.
What am I missing?
Didnt try it, and depends on exact configuration :
When you logged in on the first browser you gave facebook the permission to allow your application to access your facebook account.
If you are logged in to facebook before on the other browsers with the same user, the permission given to the app through interaction on the first browser might be sufficient.
You can try to use incognito mode on a browser, in this case you should definitely have to authorize again.

umbraco 7 - users added via back end can't login

I'm working on a reasonably fresh install of umbraco (7.1.8). I've only installed three plugins at the moment, so I don't believe they are the issue.
If I login using the id created during the install process, I can login fine. But now I want to start adding other users to allow them to add content, and I can't seem to get the users created so they can get access to the back end.
I've double and triple checked the passwords (even using the reset password and copy/pasting from one browser to the next). I've tried using both the email address and the login, but no joy in either scenario. I've tried to just make this first account an admin - no joy.
I opened the console and found this error on the console:
POST /umbraco/backoffice/UmbracoApi/Authentication/PostLogin 400 Bad Request 114ms
I'm hoping it's something glaringly obvious, but I can't see it for the life of me.
Had a similar issue a while back in version 6 where members created programmatically would not be able to login once they updated their email address. Had to ensure that the login was the same as the email address in order for them to login the next time. It is rather confusing I must admit.
Ensure login field value of user = email address field value of user

Magento Password Reset Link

We run a multi-store/view magento site. Let's say our site is called www.domain.com (running the "retail" store) and another url trade.domain.com running the "trade" store
When a customer requests a password reset from trade.domain.com, they get a password reset link like this: http://trade.domain.com/customer/account/resetpassword/?id=12&token=84fb6f65548995191e526b815982bf23
Clicking this link re-directs to login page with the error Your password reset link has expired..
However, if you replace the "trade" from the domain with "www" like this: http://www.domain.com/customer/account/resetpassword/?id=12&token=84fb6f65548995191e526b815982bf23
The password reset appears to be working correctly.
Any idea why this is happening? Have I configured the magento incorrectly? Is this a known bug?
Customers are shared either per website, either across all websites, so at least, a customer account is usable on all of the store views that a website contains. Consequently, it is normal that the password reset link works for your store views.
In fact, if you would like to separate the customer accounts between your store views, you would have to create separate websites that would not share customers.
Is that subdomain password protected? That could be a problem or if subdomain is set up with a password protected extension, they won't be able to access example.com/customer/account/changeforgotten/ without already being logged in. So you'll have to allow them access to that url first otherwise it'll keep redirecting. I had the same problem.
Check the cookie domain for the website trade.domain.com. In Magento 1 it's in System->Configuration->Web->Session Cookie Management. (Making sure that you change the scope in the top left to the Website you want to update it for.
I have a store that has multiple websites, each with their own view and does not share accounts across websites, and had the same problem. Changing the cookie path fixed it for me.

Resources