Erro no app para Android onde o formulário não abre ao tentar iniciar qualquer processo

Acontece um erro de "signature_invalid" ao tentar iniciar qualquer processo pelo App do Android e com isso o formulário não carrega. Porém o processo funciona normalmente no App do iOS e via browser.

Estou anexando prints do erro e abaixo segue trecho do log:

2018-05-05 19:17:49,001 INFO  [com.totvs.technology.wcm.core.service.PageServiceBean] (EJB ASYNC - 124) Cache cleared for page principalfavorites on tenant 1
2018-05-05 19:17:49,006 INFO  [com.datasul.technology.webdesk.util.TokenManager] (default task-11) insertToken(353d2691-c4bc-4dbc-a6b7-49c526d515ad, CLEVERSON)
2018-05-05 19:17:49,006 INFO  [com.datasul.technology.webdesk.util.TokenManager] (default task-11) findByToken 353d2691-c4bc-4dbc-a6b7-49c526d515ad
2018-05-05 19:17:49,008 INFO  [com.datasul.technology.webdesk.util.TokenManager] (default task-11) ret null
2018-05-05 19:17:49,008 INFO  [com.datasul.technology.webdesk.util.TokenManager] (default task-11) save(CLEVERSON, 353d2691-c4bc-4dbc-a6b7-49c526d515ad)
2018-05-05 19:17:49,040 INFO  [com.totvs.technology.wcm.core.service.theme.ThemeServiceBean] (EJB ASYNC - 124) [6/179] page principalfavorites changed theme to themedefault
2018-05-05 19:17:49,053 INFO  [com.datasul.technology.webdesk.util.TokenManager] (default task-11) salvo
2018-05-05 19:17:49,146 INFO  [org.jboss.security.auth.spi.AbstractServerLoginModule] (default task-11) logout - flushCache: CLEVERSON
2018-05-05 19:17:49,156 INFO  [org.jboss.security.auth.spi.AbstractServerLoginModule] (default task-11) logout - flushCache: CLEVERSON
2018-05-05 19:17:49,279 INFO  [com.totvs.technology.wcm.core.service.PageServiceBean] (EJB ASYNC - 124) Cache cleared for page pagefavorites on tenant 1
2018-05-05 19:17:49,311 ERROR [com.fluig.auth.FluigAuthenticationMechanism] (default task-1) signature_invalid: net.oauth.OAuthProblemException: signature_invalid
oauth_problem: signature_invalid
oauth_signature: Sf8rpT4hhyGgOgZOhF94xK96qHM=
oauth_signature_base_string: GET&http%3A%2F%2F104.41.45.139%3A8080%2Fwebdesk%2Fstreamcontrol%2F9595%2F0%2F0%2F&WDCompanyId%3D1%26WDNrDocto%3D0%26WDNrVersao%3D0%26WDParentDocumentId%3D9595%26WKDef%3Dbatida-ponto%26WKNumProces%3D0%26WKNumState%3D0%26WKUser%3D036%26WKVersDef%3D8%26edit%3Dtrue%26mobile%3D%26newRequestProcess%3D%26oauth_consumer_key%3Df22c4162-8408-4302-81bc-071d2edef56c%26oauth_nonce%3D2541374194023136715%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1525547833%26oauth_token%3D1b3d420d-df4c-4f01-b5cc-cb5fb1017ccc%26oauth_version%3D1.0%26processID%3Dbatida-ponto%26token%3D353d2691-c4bc-4dbc-a6b7-49c526d515ad
oauth_signature_method: HMAC-SHA1
    at net.oauth.signature.OAuthSignatureMethod.validate(OAuthSignatureMethod.java:69)
    at net.oauth.SimpleOAuthValidator.validateSignature(SimpleOAuthValidator.java:254)
    at com.totvs.technology.foundation.oauth.FluigOAuthValidator.validateSignature(FluigOAuthValidator.java:29)
    at net.oauth.SimpleOAuthValidator.validateMessage(SimpleOAuthValidator.java:148)
    at com.fluig.auth.FluigAuthenticationMechanism.authenticateOAUTH(FluigAuthenticationMechanism.java:278)
    at com.fluig.auth.FluigAuthenticationMechanism.authenticate(FluigAuthenticationMechanism.java:120)
    at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
    at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263)
    at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263)
    at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:231)
    at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:125)
    at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:99)
    at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:92)
    at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
    at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
    at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
    at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
    at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
    at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
    at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
    at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
    at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
    at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
    at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
    at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
    at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
    at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
    at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
    at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:805)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
compartilhar
  • Alguém consegue me ajudar?

    Helcio Penha   09 de May de 2018
  • estou com o mesmo problema...

    William Souza   16 de May de 2018
  • William, já conseguimos resolver. Irei postar a solução.

    Helcio Penha   16 de May de 2018
  1. Você vai ver essas setas em qualquer página de pergunta. Com elas, você pode dizer se uma pergunta ou uma resposta foram relevantes ou não.
  2. Edite sua pergunta ou resposta caso queira alterar ou adicionar detalhes.
  3. Caso haja alguma dúvida sobre a pergunta, adicione um comentário. O espaço de respostas deve ser utilizado apenas para responder a pergunta.
  4. Se o autor da pergunta marcar uma resposta como solucionada, esta marca aparecerá.
  5. Clique aqui para mais detalhes sobre o funcionamento do fluig Forum!

2 respostas

Não é a resposta que estava procurando? Procure outras perguntas com as tags android signatureinvalid ou faça a sua própria pergunta.