security - How secured is SSO based on token based authentication? -
I plan to integrate the Jasper server as a single sign on with my web application. I went through and jasper suggests token based authentication as a solution (as authentication is already done by my web application)
what Jaspar has suggested
As a token (defined below tokenformat mapping) in a specific format, you will certify a gypser request from astrology server.
Can be a valid token
U = User | R = role1 O = org1 Pa1 = PA11 | Pa2 = PA21 Exp = 2001404150601 can cause invalid token
u1 = user | R = role1 O = org1 Pa1 = PA11 | Pa2 = PA21 Exp = 2001404150601 r = Role 1 | U = User | O = org1 Pa1 = PA11 | Pa2 = PA21 Exp = 2001404150601 My question is actually a safe process because as soon as the hacker knows the pattern, he can simply log on to the jasper server? I think there can be a compromise with security here. Am I missing something here?
Bean square = "com.jaspersoft.jsperserver.api.security.externalAuth.wrappers.spring.preauth.JSPreAuthenticatedAuthenticationProvider" & gt; .................... & lt; Property Name = "TokenPierShiper" value = "|" / & Gt; & Lt; Property Name = "Token Format Mapping" & gt; & Lt; Map & gt; & Lt; Entry key = "user name" value = "u" /> & Lt; Entry key = "roles" value = "r" /> & Lt; Entry key = "orgId" value = "o" /> & Lt; Entry key = "end time" value = "closing" /> & Lt; Entry key = "profile. Authorization" & gt; & Lt; Map & gt; & Lt; Entry key = "profile attribute 1" value = "pay1" /> & Lt; Entry key = "profile ATTB2" value = "pay2" /> & Lt; / Map & gt; & Lt; / Entry & gt; & Lt; / Map & gt; & Lt; / Property & gt; & Lt; Property Name = "Tokens Exacttimestamp Format" Value = "yyyyMMDHHmmssZ" /> & Lt; / Bean & gt; & Lt; / Property & gt; & Lt; / Bean & gt; According to, the user is not directly signed using token-based authentication, according to which,
In addition, this specifies the following:
The JasperReports server will accept any properly formatted token ; Therefore, you need to protect the integrity of the token using the following measures like:
- Connect to JasperReports server using SSL to protect against token blocking < / Strong>.
- Token to protect from tampering Encrypt
- Token to use a timestamp to protect against replay attacks Configure without the timestamp, when you include a token in the web page or REST web service URL, the URL can be copied and used by unauthorized people or systems. Setting the end time for the token will prevent the token / URL from being used to authenticate over the specified time. You can set the closing time on the basis of usage. Requesting access to the user / application and JasperReports server, the expiration period for one minute or less is appropriate from the request time.
All communication should be made through an SSL tunnel; otherwise, anyone can establish a connection to your JR server, send a token and get information about it. Can do.
Comments
Post a Comment