These are chat archives for spring-cloud/spring-cloud

18th
Oct 2016
Dave Syer
@dsyer
Oct 18 2016 06:17
If you trust the worker process you have no option but to allow it to impersonate the user (e.g. give it a full refresh token). If you don't trust it, you also have no option but to ask a user for authorization before it executes.
Sharif Ghazzawi
@Sghazzawi
Oct 18 2016 14:28
@dsyer thanks, that's the path I was going down but wanted to make sure there weren't some options/patterns/solutions I was missing.
pradeepkusingh
@pradeepkusingh
Oct 18 2016 14:39
@spencergibb , I am trying to upgrade my apps from Springboot 1.2.8+ Angelsr6 to Springboot 1.4.1+ Camden and seeing below error error..
OUT Tue Oct 18 14:35:58 UTC 2016 ERROR [APP:null TRACKING_ID:null ACCOUNT_NUM:null] com.netflix.discovery.shared.transport.decorator.RedirectingEurekaHttpClient.execute - Request execution error ERROR_DETAILS: com.sun.jersey.api.client.ClientHandlerException: A message body reader for Java class com.netflix.appinfo.InstanceInfo, and Java type class com.netflix.appinfo.InstanceInfo, and MIME media type text/plain; charset=utf-8 was not found at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:630) at com.sun.jersey.api.client.ClientResponse.getEntity(ClientResponse.java:586) at com.netflix.discovery.shared.transport.jersey.AbstractJerseyEurekaHttpClient.sendHeartBeat(AbstractJerseyEurekaHttpClient.java:105)
I can see jersy libraries in apps. not sure why seeing this error
Heiko Scherrer
@openwms
Oct 18 2016 16:53

Hi all. I've a configserver bootstrapped without further customizations (just serviceId, label & security). The client application can access the config but too late, even the configserver setup on c/s is defined in the bootstrap phase (bootstrap.yml). The defined Spring Integration beans are not getting the properties wired although the log shows the following lines after the Spring Boot banner:

<<< Banner >>>
2016-10-18 18:32:24.084  INFO [34757/1] - c.c.c.ConfigServicePropertySourceLocator : Fetching config from server at: http://hamunaptra:8099/
2016-10-18 18:32:24.674  INFO [34757/1] - c.c.c.ConfigServicePropertySourceLocator : Located environment: name=tcpip-driver, profiles=[default], label=ZILE, version=16b0d10f4ef76d92c85aa34d9145ac110d0c75dd

Any ideas what I do wrong?

client config looks like:
owms:
  eureka:
    password: sa
  driver:
    server:
      port: 50000
      so-timeout: 500000
      so-receive-buffer-size: 160
      so-send-buffer-size: 160

spring:
  main:
    banner-mode: off
  application:
    name: tcpip-driver
  cloud:
    config:
      discovery:
# Enable configserver over eureka
        enabled: true
# Name of configserver is customized
        serviceId: openwms-config
# Set the project name (Github branch) to get the config from
      label: ${owms.tenant:master}
      fail-fast: true

server:
  port: 8084

eureka:
  client:
    serviceUrl:
# Where to lookup the configserver
      defaultZone: ${vcap.services.eureka.credentials.uri:http://${owms.eureka.username:user}:${owms.eureka.password:}@${owms.eureka.host:127.0.0.1}:${owms.eureka.port:8761}}/eureka/
  instance:
    metadataMap:
# Username and password passthrough to configserver
      username: ${owms.eureka.username:user}
      password: ${owms.eureka.password:}
-retry and -aop are on the CP.