Same aggregate in 2 bounded contexts

Let's model this scenario: We are trying to connect to different "Suppliers" via FTP. Each Supplier can have 1 or more FTP servers. We are going to download Inventory files from these FTP servers. 

 I can identify 2 bounded contexts in this domain:
 Suppliers Bounded Context where I mange the life cycle of adding or disabling/enabling a supplier.  Suppliers Communication Bounded Context where  connect and download the inventory files from the ftp servers.In BC 1, Supplier is an entity with a model that has id, name, description,...etc. I think I'll also add a Supplier Type since we may need to connect to other supplier via different protocols other than ftp.
 

 The problem is with BC 2. Is Supplier an entity? 
 

 The FTP info (host, port, user, pass) is stored in BC 2 and I believe it's a value object. However, this value object should be tied to an entity. If I make Supplier an entity I'm guessing the only attribute it will need is the supplier id from BC 1. 
 

 Does that make sense to have the same entity in 2 bounded contexts? Is it normal that the only attribute to be present in entity is the id?