Access tokens follow the same rules as regular Salesforce session IDs - they have an idle timeout that is set in Setup | Administration Setup | Session Settings | Session Timeout. The default session timeout is 2 hours, but an org admin can set it to any of a variety of values from 15 minutes to 8 hours. See https://login.salesforce.com/help/doc/user_ed.jsp?loc=help&target=admin_sessions.htm§ion=Securit... for more details
Access tokens follow the same rules as regular Salesforce session IDs - they have an idle timeout that is set in Setup | Administration Setup | Session Settings | Session Timeout. The default session timeout is 2 hours, but an org admin can set it to any of a variety of values from 15 minutes to 8 hours. See https://login.salesforce.com/help/doc/user_ed.jsp?loc=help&target=admin_sessions.htm§ion=Securit... for more details
Hi chinnu,
Access tokens follow the same rules as regular Salesforce session IDs - they have an idle timeout that is set in Setup | Administration Setup | Session Settings | Session Timeout. The default session timeout is 2 hours, but an org admin can set it to any of a variety of values from 15 minutes to 8 hours. See https://login.salesforce.com/help/doc/user_ed.jsp?loc=help&target=admin_sessions.htm§ion=Securit... for more details
All Answers
I'm not sure what you're asking here. The auth token can be used with the REST API, as long as your organization has access to the API.
Hi chinnu,
Access tokens follow the same rules as regular Salesforce session IDs - they have an idle timeout that is set in Setup | Administration Setup | Session Settings | Session Timeout. The default session timeout is 2 hours, but an org admin can set it to any of a variety of values from 15 minutes to 8 hours. See https://login.salesforce.com/help/doc/user_ed.jsp?loc=help&target=admin_sessions.htm§ion=Securit... for more details