The direction you'll want to be heading is letting the users allow your app access once. You can then store the user's oAuth token and oAuth token secret with their account. (instead of their username and password) These won't change unless the user revokes your website's access.
jarón On Feb 1, 11:51 am, Archia <tomarchib...@gmail.com> wrote: > I have a web application to allow clients to update information for their > recordings (music) which are then listed on another site. I'd like to > include an area to allow them to update their Twitter status. Given that > each client already signs in to the current application, and (some of) their > Twitter usernames and passwords are already in a database, it would be good > if they did not need to log in to Twitter as well and select 'Allow' each > time they visit that area of the application. Is it possible to bypass the > Sign in with Twitter step on connect.php and somehow send their username and > password, or at least only require this once and store their credentials in > the database to be used thereafter? > > Thanks! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
