What is my goal: every guest (user which has not got token in DB) should be displayed as logged in as some account, let's say "test". And he can do everything like normal user (because he is). But he can just log off and turn to another account or browse site anonymously.
Is it possible to do it with stock Kohana 3.3 Auth? I need this to finish my google adsense approval process.
Put this line at the start of the parent controller:
Auth::instance()->login('test', 'test', false);
Related
Does IBM Domino track the last login date for web users(UserName/Password and internet certificate)? I know the access logs contains this information but wanted to know if there may be something built into Domino (maybe in Address Book). Trying to come up with a method to disable web accounts that have not accessed a domino server in a specified time period.
Thanks,
Kev
The User Activity area in the Database Properties picks up from the log.nsf, which is where this information is stored. But, typically, the log.nsf will only have a few days' worth of information. When I've had this requirement before, I've manually captured it via a custom login page or an initUser function I've had in applications.
One of the easiest solutions is to trigger an action from a live web page that generates a database.nsf?openagent event.
like:
or
Ideally you've use the openagent to print a content type and a response, but if you don't browsers do pretty well with invalid responses from servers.
inside your "myagent" you will have the users name available to you to write it to a document.
Your next challenge will be in getting the agent to trigger, but, not too often, ideally only on login.
When a user uses a custom login form it submits the username/password and redirection url in POST method. You could change that to ...?openagent&nexturl=/blablabla.nsf
Your tiny little agent would run one and only one time upon login and update a document in a your custom logging database.
That's a developer's solution.
There are also admin solutions. The server does keep track of active web sessions, but, it does not drop them into the log.nsf like it does upon session ending for a notes session. I don't think it would be too much work from an admin standpoint to get that information there are a lot of event triggers available to you. It's just been way too long since I worked on any server that anyone cared about statistics.
Before the Instagram policy changes (which made on June 1, 2016) my application showed a list of all the following users' info of the logged in user. I get this by the following URL GET request:
https://api.instagram.com/v1/users/self/follows?access_token=ACCESS-TOKEN
After the changes, I get a list of only the Sandbox users the logged on user is following after. (I added Sandbox user to keep developing this app).
But, in fact, I want to get all the users' info the logged on user is following after.
If it only happens in Sandbox environment it's OK but what about the production environment?
After I submitted my app, can I get all the following list? Or I'll get only the users who logged in to my app (like Facebook does)?
Thank You
Krisrak's answer is correct, sandbox mode is why you are not seeing results. Here's a bit more details on how it works:
NOTE: What follows is explained more clearly in this summary of how the new Instagram API rules
“Sandbox mode” is the (unintuitively-named) gatekeeper walling off
most of what you want to do. This is the default status for all
clients, that have not undergone the strict submission process. An API
client in sandbox mode has extremely limited permissions. In fact, it
has fewer permissions than an anonymous user viewing public content
because your app basically lives on a tiny desert island in which you
are the only Instagram user and only your past twenty posts exist. So,
for example, the /media/search endpoint will only return the media you
uploaded near a given location, excluding the media from everyone else
or any posts beyond your last twenty.
...
Sandbox users are other Instagram users that you “invite” to your
client. The main reason to do this is so that your app will then be
able to “see” their last twenty posts in addition to your own. In
other words, when they accept the invitation, they show up on the tiny
desert island where your app lives.
In production mode, you will see all the users, in sandbox mode you will only see the users that you have added to sandbox.
I am getting an error saying I am not logged in to the server when attempting to submit my vehicle to the http://challenge-na.coderallycloud.com contest server. When I bring up the server list it shows that I am Online and logged in using my userid.
When I test the connection it is successful.
Unable to submit vehicle (after 10-15 minutes)
Unable to enter ChrisHanksCarOne on NA Contest Service
You need to login to the server before continuing to race. In the Code Rally Developer View choose the server list, right-click on the server and click login.
Sounds like the OAuth login hasn't worked properly, and the Eclipse plugin hasn't detected that. To fix log out from the server and login again (you can do this from the servers window or through the bottom of the enter race window). You should be asked to authenticate with Google, Facebook or Twitter - use the account you registered with on InfoQ and it should work (if not let me know and I can look into it further).
" How can I prevent users to login twice from different machines? The Users should only be allowed to login once on the machine. Once he or she login into different machine, the previous machine will logout automatically. How can be implement in magento. is there any plugin that will do this task ???
There is a section "Online Customers" under Customers in Admin.
Here magento shows name, email, ip address, session start time, last activity and last url accessed.
you can call 'log/visitor_online' model and get list of all currently online customers/ visitors.
Now whenever a customer logs in, you can make a custom observer and call its function to match email of that customer with all this data you got from model.
and logout cutomer from previous device if you find a record same.
Hope you understand my point.
I wrote a small extension to enforce the rule you're looking for - allow an admin user to have only one active session. It's a beta release, so test thoroughly.
https://github.com/siliconrockstar/magento-admin-single-session
I'm facing an extrange behavior in my Sharepoint 2077 farm:
We have configured windows integrated authentication with NTLM, and all clients authenticates correctly to the portal.
When they proceeds to "login as" diferent user, it seems to be all fine (appears user name in top of page) , but internally the page user is the old user. I know this because I have a customized web page that reads page user name and print it to the page.
after some refresh or waiting some time, the current user is applied "internally" too.
Do you know is there is any configuration option for avoid this delay?
Many thanks in advance,
any help would be appreciated.
solved there:
http://support.microsoft.com/default.aspx/kb/970814