When does on should consider implementing the Single sign on in an application.

Can you elaborate a bit more?  

The largest issue with SSO is the "keys to the kingdom" dilemma.  SSO is great for alleviating the need to remember a dozen passwords.   Users with too many passwords tend to write them down, use weak passwords, use the same password for everything, etc.  SSO allows them to use a single password to get in to everything, which is great so long as this single password is strong.  The downside is if that single password is compromised then every application the user has access to is also compromised.  This can be mitigated by using multi factor authentication, such as the saved SSO password and a token.

we are having one web application and support reports also.

managment asked me to consider the option putting sso for running the reports.
I really confused what exactly this means?

I am new to web environemnt, please advive getting mein understand this?

also what exactly meaning of single-sign on keeping off and
                                               single -sign on keeping on.

thanks for your adive

is there any update from experts on this

answer provided is quite OK